Want to import data from JSON Lines (JSONL / NDJSON / LDJSON) file to Redshift?
Try Withdata FileToDB, a desktop JSONL to Redshift converter for Windows, MacOS, and Linux, Import JSON Lines to Redshift, 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 locally and privately, avoid uploading large or private JSONL file(s) to online services.
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.
Import data from JSON Lines (JSONL / NDJSON / LDJSON) file to Redshift
Login to Redshift -> Choose JSON Lines file -> Set Redshift table -> Import JSON Lines to Redshift
Choose Redshift and logon.
Click “Wizard – 1 File To 1 Table” at task dialog.
Select the “JSON” file type.
then show the wizard.
1. Open a JSON Lines (JSONL / NDJSON / LDJSON) file.
Support large ( > 4GB ) JSON Lines file.
Here is the file’s content.
FileToDB will parse JSON Lines file.
2. Select a Redshift table and config fields.
3. Preview data will be in Redshift table.
4. Import JSON Lines data to Redshift.
View imported data in Redshift table
Convert JSON Lines (JSONL / NDJSON / LDJSON) to Redshift in command line
Save “JSON Lines to Redshift” session, then you can:
- Import JSON Lines (JSONL / NDJSON / LDJSON) to Redshift in Windows command line.
- Import JSON Lines (JSONL / NDJSON / LDJSON) to Redshift in Linux command line.
- Import JSON Lines (JSONL / NDJSON / LDJSON) to Redshift in macOS command line.
Set scheduled tasks for converting JSON Lines (JSONL / NDJSON / LDJSON) to Redshift
You can schedule and automate this “JSON Lines to Redshift” conversion task by:
- Save session and create .bat (Windows) or .sh (Linux/macOS) file for “JSON Lines to Redshift” conversion.
- Set scheduled task for “JSON Lines to Redshift” conversion.
FAQ
More tools for JSONL / NDJSON / LDJSON.
Download Withdata FileToDB
JSON Lines → Redshift reference
Type mapping
| Value kind | in JSON Lines | in Redshift |
|---|---|---|
| Int | 1234 (number) | integer |
| Bigint | 9007199254740993 | bigint |
| Decimal | 1234.56 (number) | numeric(p,s) |
| Float | 1.234e10 (number) | double precision |
| Text | "text" (string) | varchar(n) |
| Long text | "multi-line\ntext" | varchar(max) |
| Date | "2026-09-18" (string) | date |
| Datetime | "2026-09-18T14:30:00Z" (string) | timestamp |
| Binary | "base64:..." (string) | (none) |
| Boolean | true / false (boolean) | boolean |
| JSON | nested object on the same line | super |
Dialect differences
JSON Lines is a file format and Redshift is a database server, so the target has to be told the types the file never carried - the rows below are where the two sides diverge.
| Property | in JSON Lines | in Redshift |
|---|---|---|
| port | — | 5439 |
| identifiers | Double quotes; backslash escapes (a newline inside a string... | "double quotes" |
| row limit | — | LIMIT n |
| dates | No date type: dates arrive as strings | timestamp, date |
| long text | — | VARCHAR(MAX) |
| 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 | Flat stream | Tables of rows and columns |
| ceiling | Streams, so it scales past what a single JSON document can ... | — |
Command line
| Side | Command |
|---|---|
| Redshift | UNLOAD to S3 |
| Redshift (load) | COPY from S3 |
No counterpart
- JSON Lines values of kind Binary have nowhere to go in Redshift.
Convert your data online, free
Free in-browser converters for CSV, Excel, JSON, XML and SQL: Withdata Online Data Conversion. Large files, batch conversion or scheduling? See the offline desktop apps, or browse all data conversion tools.
