NDJSON JSONL Compressor
Create a local .jsonl.gz archive or restore its original UTF-8 payload. Compare byte totals and check the BOM, line break counts and final line status.
Verify Exact JSONL Bytes After GZIP Extraction
Archive UTF-8 text byte for byte, including malformed records, mixed line endings and a UTF-8 byte order mark.
NDJSON JSONL Compressor: how to use it
- Open the original UTF-8 text file for exact byte preservation, or paste text to archive the editor contents.
- Select Compress to GZIP. Review the framing counts and download the .jsonl.gz archive.
- Use output to extract or open a previously saved GZIP. Download the restored JSONL and compare its bytes with the input.
Limits and notes
Uses one GZIP member, up to 9 MB compressed and 8 MB of UTF-8 payload. A small archive can be larger than its source. It checks UTF-8 decoding and preserves empty, blank, valid and malformed lines as supplied. JSONL syntax validation is available in the log parser or validator.
How your privacy works →NDJSON JSONL Compressor: common questions
Will archiving remove a BOM, blank line or malformed record?
The payload keeps every UTF-8 byte, including BOM and line endings. Review or repair the source in a separate workflow when compatibility requires it.
What if my last record has no newline?
Extraction preserves that exact ending. Check Terminal line break in the framing summary.
Can I expand an archive produced elsewhere?
Open a compatible single-member GZIP containing UTF-8 up to the expansion limit. Damaged or oversized files produce an error instead of a partial download.