Want to convert TXT to JSON lines (JSONL / NDJSON / LDJSON)?
Try Withdata Data File Converter, a desktop TXT to JSON converter for Windows, MacOS, and Linux, Convert TXT to JSON lines, Easy and Fast.
- Can run in GUI mode, Step by Step, just a few mouse clicks.
- Can run in Command line, for Scheduled Tasks and Streams.
- Convert files locally and privately, avoid uploading large TXT file(s) to online services.
Download DataFileConverter
Windows 64 bit
Windows 32 bit
Linux .deb (For Debian, Ubuntu) 64 bit
Linux .rpm (For Red Hat, Fedora, SUSE) 64 bit
MacOS 64 bit
JSON Lines text format (JSONL), also called Newline-delimited JSON (NDJSON), or Line-delimited JSON (LDJSON). JSON Lines files may be saved with the file extension .jsonl, *.ndjson, *.ldjson.
Convert TXT to JSON lines (JSONL / NDJSON / LDJSON)
Choose TXT file -> Set target JSON Lines (JSONL / NDJSON / LDJSON) file -> Convert TXT to JSON lines (JSONL / NDJSON / LDJSON)
Click “Start a New Convert” at task dialog.
then show the wizard.
Select source/target file type.
1. Open a TXT file.
The TXT content:
2. Config target JSON Lines (JSONL / NDJSON / LDJSON) file.
3. Set rows options.
4. Convert TXT to JSON lines (JSONL / NDJSON / LDJSON).
See JSON lines file
Convert TXT to JSON lines (JSONL / NDJSON / LDJSON) in command line
Save “TXT to JSON Lines” session, then you can:
- Convert TXT to JSON lines (JSONL / NDJSON / LDJSON) in Windows command line.
- Convert TXT to JSON lines (JSONL / NDJSON / LDJSON) in Linux command line.
- Convert TXT to JSON lines (JSONL / NDJSON / LDJSON) in macOS command line.
Set scheduled tasks for converting TXT to JSON lines (JSONL / NDJSON / LDJSON)
You can schedule and automate this converting task by:
- Save session and create .bat (Windows) or .sh (Linux/macOS) file for “TXT to JSON lines” conversion.
- Set scheduled task for “TXT to JSON lines” conversion.
FAQ
More tools for JSONL / NDJSON / LDJSON.
Download Withdata DataFileConverter
Windows 64 bit
Windows 32 bit
Linux .deb (For Debian, Ubuntu) 64 bit
Linux .rpm (For Red Hat, Fedora, SUSE) 64 bit
MacOS 64 bit
TXT → JSON Lines reference
Type mapping
| Value kind | in TXT | in JSON Lines |
|---|---|---|
| Int | 1234, or right-aligned in a fixed-width column | 1234 (number) |
| Decimal | 1234.56 | 1234.56 (number) |
| Float | 1.234e+10 | 1.234e10 (number) |
| Text | written as-is; padding depends on the chosen layout | "text" (string) |
| Long text | written as-is | "multi-line\ntext" |
| Date | whatever the writer chose | "2026-09-18" (string) |
| Datetime | whatever the writer chose | "2026-09-18T14:30:00Z" (string) |
| Binary | not representable | "base64:..." (string) |
| Boolean | Y / N, or 1 / 0, or TRUE / FALSE | true / false (boolean) |
| JSON | written as-is | nested object on the same line |
Dialect differences
Both TXT and JSON Lines are file formats, so what differs below is how each one chooses to represent a value.
| Property | in TXT | in JSON Lines |
|---|---|---|
| identifiers | None by convention | Double quotes; backslash escapes (a newline inside a string... |
| dates | Whatever the writer produced; no convention is guaranteed | No date type: dates arrive as strings |
| binary | Not supported | Not supported natively - base64 inside a string |
| separator | Whatever was chosen - often fixed column widths | Newline between records |
| encoding | No declaration - UTF-8 works only with a BOM | UTF-8 by definition |
| typing | None - every field is text | Same as JSON, but records cannot nest across lines |
| shape | Free form; a parser has to be told the layout | Flat stream |
| ceiling | No formal limit | Streams, so it scales past what a single JSON document can ... |
Data File Converter without the manual work
For batch jobs, large files and scheduling use the Data File Converter converter — an offline desktop app for Windows, Linux and macOS. Free trial.