JSONL Lifeboat — preserve good records after a bad line

1. Add JSONL

Open a local .jsonl, .ndjson, or .txt file Paste JSONL text

2. Choose policy

Accept any valid JSON valueOff by default. Otherwise only top-level objects are accepted; arrays, scalars, and null remain valid but rejected. Include raw rejected lines in local downloadOff by default. The on-screen table and report.json never contain raw values. Invalid UTF-8 bytes are always omitted.

Lines over 1 MiB are parsed first. Valid oversized objects remain accepted with a warning; they are never mislabeled malformed only because of size.

Ready. Nothing has been loaded.

Value-free results

3. Review and download

Line report. Raw values are never shown.
Line	Bytes	Classification	Policy	Error category	Offset

accepted.jsonl preserves accepted line bytes and order, removes CR terminators, and joins records with LF. The source file is never modified.

Bounded manual help

Need a custom recovery/schema profile?

USD 15 for a profile based on a redacted sample, up to 3 record types, with 1 revision. This is manual assistance—not automatic repair, schema correctness, secret detection, or forensic recovery.

Email about the profile Do not attach production logs, secrets, or personal data to the first email.

Scope and limits

This v1 diagnoses and separates lines locally. It does not edit records, prove schema correctness, guarantee secret detection, provide complete forensic recovery, store files, or send data anywhere.