Want to convert each table data in a SQL file to a separate JSON file at one time?
Try Data File Converter, a SQL converting tool for Windows, MacOS, and Linux, Convert tables in a SQL file to JSON files, 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 SQL file(s) to online services.
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
Convert each table data in a SQL file to a separate JSON file
Select source SQL file -> Set target JSON file -> Convert SQL table to JSON
Click “Start a New Convert” at task dialog.
then show the wizard.
Select From “File” “SQL” To “Files” “JSON”.
1. Open a source SQL file, select tables to convert to JSON files.
2. Config target JSON files.
3. Summary.
List selected tables.
4. Convert each SQL table to a separate JSON file.
After converting, you can view output JSON files.
Convert each SQL table to a separate JSON file in command line
Save “SQL table to JSON” session, then you can:
- Convert each SQL table to a separate JSON file in Windows command line.
- Convert each SQL table to a separate JSON file in Linux command line.
- Convert each SQL table to a separate JSON file in macOS command line.
Set scheduled tasks for converting each SQL table to a separate JSON file
You can schedule and automate this SQL table to JSON converting task by:
- Save session and create .bat (Windows) or .sh (Linux/macOS) file for “SQL table to JSON” conversion.
- Set scheduled task for “SQL table to JSON” conversion.
FAQ
More about Withdata DataFileConverter – Tables in SQL file to JSON converter
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
See Video: Convert each table data in a SQL file to a separate JSON file at one time
SQL → JSON reference
Type mapping
| Value kind | in SQL | in JSON |
|---|---|---|
| Int | INT | 1234 (number) |
| Bigint | BIGINT | 9007199254740993 |
| Decimal | DECIMAL(p,s) | 1234.56 (number) |
| Float | DOUBLE PRECISION | 1.234e10 (number) |
| Text | VARCHAR(n) | "text" (string) |
| Long text | TEXT / CLOB | "multi-line\ntext" (escaped newline inside a string) |
| Date | DATE | "2026-09-18" (string) |
| Datetime | TIMESTAMP | "2026-09-18T14:30:00Z" (string) |
| Binary | BLOB / BYTEA | "base64:..." (string) |
| Boolean | BOOLEAN / SMALLINT | true / false (boolean) |
| JSON | JSON / TEXT | nested object or array, kept as structure |
Dialect differences
Both SQL and JSON are file formats, so what differs below is how each one chooses to represent a value.
| Property | in SQL | in JSON |
|---|---|---|
| identifiers | Two competing conventions: single-quoted literals and diale... | Double quotes; backslash escapes |
| dates | Depends on the dialect: DATE literals, TO_DATE(), or plain ... | No date type: dates arrive as strings and the reader must p... |
| binary | Dialect-specific: X-quoted literal, 0x hex, or decode() | Not supported natively - base64 inside a string |
| separator | Statement terminators (;) | Braces and commas |
| encoding | No declaration | UTF-8 by definition |
| typing | Types belong to the target database, and they differ betwee... | string, number, boolean, null, object, array - no date type |
| shape | Statements; a dump usually means CREATE TABLE plus INSERT rows | Nested objects and arrays |
| ceiling | No formal limit, but a single INSERT statement has to fit i... | Whole document is usually parsed into memory |
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.