Want to export data from DBF table to JSON lines (JSONL / NDJSON / LDJSON)?
Try Withdata DBToFile, Support Windows, Linux, and macOS, Export DBF data to JSON lines (JSONL / NDJSON / LDJSON), 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.
- Support Windows, Linux, and macOS.
Download Withdata DBToFile
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.
Export data from DBF table to JSON lines (JSONL / NDJSON / LDJSON)
Login to DBF -> Choose DBF table -> Set JSON lines file options -> Export DBF to JSON lines (JSONL / NDJSON / LDJSON)
Choose DBF and logon.
“Export From Table” for “DBF to JSON lines (JSONL / NDJSON / LDJSON)”.
Select JSON file type.
1. Choose DBF table.
2. Set JSON lines (JSONL / NDJSON / LDJSON) file options.
3. Set rows options.
4. Export DBF data to JSON lines (JSONL / NDJSON / LDJSON) table.
After exporting, you can view output JSON lines (JSONL / NDJSON / LDJSON) file.
More tools for JSONL / NDJSON / LDJSON.
Download Withdata DBToFile
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
DBF → JSON Lines reference
Type mapping
| Value kind | in DBF | in JSON Lines |
|---|---|---|
| Int | Numeric(10,0) | 1234 (number) |
| Bigint | Numeric(19,0) | 9007199254740993 |
| Decimal | Numeric(p,s) | 1234.56 (number) |
| Float | Float | 1.234e10 (number) |
| Text | Character(n) | "text" (string) |
| Long text | Memo | "multi-line\ntext" |
| Date | Date | "2026-09-18" (string) |
| Datetime | (none) | "2026-09-18T14:30:00Z" (string) |
| Binary | (none) | "base64:..." (string) |
| Boolean | Logical | true / false (boolean) |
| JSON | (none) | nested object on the same line |
Dialect differences
DBF is a database server and JSON Lines is a file format, so the gap is wider than a dialect difference - the rows below are where values and structure stop lining up.
| Property | in DBF | in JSON Lines |
|---|---|---|
| port | (file-based) | — |
| identifiers | — | Double quotes; backslash escapes (a newline inside a string... |
| row limit | (driver dependent) | — |
| dates | Date (D) | No date type: dates arrive as strings |
| long text | Memo (M) | — |
| binary | — | Not supported natively - base64 inside a string |
| separator | — | Newline between records |
| encoding | — | UTF-8 by definition |
| typing | — | Same as JSON, but records cannot nest across lines |
| shape | Tables of rows and columns | Flat stream |
| ceiling | — | Streams, so it scales past what a single JSON document can ... |
No counterpart
- JSON Lines has no equivalent for Date and time - it has to be flattened or dropped.
- JSON Lines has no equivalent for Binary - it has to be flattened or dropped.
- JSON Lines has no equivalent for JSON - it has to be flattened or dropped.
DBF to CSV without the manual work
For batch jobs, large files and scheduling use the DBF to CSV converter — an offline desktop app for Windows, Linux and macOS. Free trial.