How to Translate JSONL Files Without Breaking Line-by-Line JSON

A practical JSONL translation workflow for preserving one valid JSON object per line, stable keys, placeholders, and review context.

Step-by-step workflow

1. 01Inspect a sample of JSONL lines to identify translatable fields and protected fields.
2. 02Keep each source line matched to exactly one translated output line.
3. 03Preserve keys, IDs, placeholders, and machine-readable values.
4. 04Validate that every translated line can still be parsed as JSON.
5. 05Run a row count and sample review before using the translated JSONL file in production.

What to protect during translation

• One JSON object per line and the original line count.
• Keys, IDs, timestamps, URLs, placeholders, and enum-like values.
• Escaped characters and embedded JSON strings inside value fields.

Pre-export checks

• Parse every line, not just the first line.
• Compare source and target line counts.
• Sample translated value fields from the beginning, middle, and end of the file.

Common mistakes to avoid

• AvoidMerging multiple JSONL lines into one block of JSON.
• AvoidChanging object keys, IDs, or placeholder names during translation.
• AvoidOnly validating the first line instead of checking every translated line.