Understand how nested objects, arrays, tables, page breaks and document settings affect your final PDF.
Converting nested JSON objects to a readable PDF
Nested JSON is common in API responses and configuration files. Formatted JSON mode preserves the hierarchy through indentation, while key-value report mode converts each nested value into a path. For example, an address object can become customer.address.city: London. The report approach removes visual brace complexity, but the formatted approach is better when the exact JSON structure matters.
Converting JSON arrays into PDF tables
If the root value is an array of objects, the converter scans the records for column names. Each object becomes a row and each detected key becomes a column. Simple values are printed directly. Nested objects and arrays are represented as compact JSON text inside their cells. Tables are convenient for uniform records, but they are not ideal for highly irregular objects where every row uses a different schema.
Handling long strings and large values
Long descriptions, encoded content, stack traces and URLs can create large PDF cells or many wrapped lines. A smaller font, landscape orientation and a larger page format can help. When the JSON contains Base64 images or binary-like strings, consider excluding those values from the report because they add many pages without improving human readability.
Choosing A4, Letter or Legal page size
A4 is widely used internationally, while US Letter is common in the United States and Canada. Legal paper provides extra vertical space. Orientation matters more than paper length for tables: portrait is usually suitable for formatted JSON and reports, while landscape gives tables more horizontal space.
Preserving Unicode and special characters
JSON supports Unicode text. Common Latin characters and many symbols display correctly with the built-in PDF font, but complex scripts, specialist glyphs and emoji may require an embedded Unicode font in a production workflow. This browser tool focuses on common text reporting and does not claim universal font coverage for every writing system.
Creating PDF records from API responses
Before converting an API response, remove sensitive headers and values that should not appear in a permanent document. Add a descriptive title such as “Inventory API Response — 30 August 2026” and keep the source JSON alongside the PDF. The source supports future automation; the PDF supports review and evidence.
JSON to PDF versus JSON to CSV
CSV is usually better when the goal is spreadsheet analysis and the data is naturally tabular. PDF is better when the goal is a controlled document that should look consistent when opened or printed. For nested structures, JSON retains more meaning than CSV. A useful workflow is to keep JSON as the master, generate CSV for analysis and create PDF for human review or filing.
Best practices for dependable JSON reports
- Validate the JSON before formatting or conversion.
- Remove secrets and data that the recipient does not need.
- Choose formatted JSON for technical accuracy, report mode for readability, or table mode for uniform records.
- Use a clear title and filename that identifies the dataset and date.
- Open the downloaded PDF and verify page breaks, characters and table columns before distribution.
- Retain the original JSON as the authoritative machine-readable source.