Parsing Large Zendesk JSON/NDJSON Exports Safely in the Browser

Zendesk full exports are useful for audits, migrations, and historical review, but they are not always pleasant to inspect.

A file ending in .json may actually be newline-delimited JSON (NDJSON): one complete object per line rather than one large JSON document. Exports can also be split across files, wrap tickets in different container shapes, or reference attachments that are not present in the archive.

I recently built a browser-local viewer for this workflow. This article covers the parsing decisions that mattered most, including the failure modes I would handle before trusting an export.

1. Do not assume .json means one JSON document

The first useful distinction is between standard JSON and NDJSON.

Parsing Large Zendesk JSON/NDJSON Exports Safely in the Browser

Related reading

Reading 50MB JSONL logs with a viewer in 2026

Your Next.js API Route Is Leaking Diagnostics in Its 400 Responses

How to Stream & Flatten 1GB+ JSON to CSV in the Browser Without Memory Leaks

How to Import JSON into MongoDB and Export to CSV with Data Masking

Stop Feeding Agents Raw Data

I Built a Fast, Privacy-First JSON Formatter with Next.js