PostgreSQL backup table to JSON
Extract one table from a PostgreSQL plain SQL COPY dump as JSON.
Drop your files here
Make something new. Keep everything private.
Multiple files welcome · processed one at a time
Select a tool to see its supported formats and conversion limits. Large files may exceed your browser’s memory.
Before processing large files
On phones and tablets, start with files under 20 MiB and keep this tab in the foreground. Video, OCR and 3D operations can use several times the input size in memory. Desktop browsers generally have more room, but the 128 MiB job limit is not a guarantee that every file will fit. Smaller batches reduce memory pressure.
Supported input formats
- SQL text dump (.sql)
- PostgreSQL plain SQL dump (COPY data) (.dump)
- PostgreSQL plain SQL backup (COPY data) (.backup)
Output format
JavaScript Object Notation (.json)
Support applies to this conversion direction. Check the limits below for features that may change or be discarded.
Compare all supported formats and conversion limits →How to use PostgreSQL backup table to JSON
- Add your supported file using the chooser or drop zone.
- Review the settings and conversion limits before processing.
- Select Convert files, then download the result.
What to expect
- Plain UTF-8 SQL dumps with text-mode COPY FROM stdin data only. Custom PGDMP, tar/directory archives, INSERT-based dumps and non-UTF-8 dumps are unsupported; use pg_restore or pg_dump to export plain SQL first. SQL is never executed.
- Maximum 64 MiB, 1,000 tables, 100,000 rows per table and 2 million total cells. Values remain text; JSON preserves SQL NULL, while CSV represents NULL as an empty cell.
Engine: PostgreSQL COPY reader. The engine may need a first-use download. Your file stays in this browser session.Check conversion engines and offline requirements.
Conversion settings
These settings are available in the converter above.
- Exact table name (inspect the database first)
About this conversion
Is postgresql backup table to json free?
Yes. This tool runs on your device without an account or a conversion fee.
Are files uploaded during conversion?
File processing happens locally in your browser. Engines may download their code on first use; your input files are not sent to a conversion server. Read how file privacy works.
What if conversion fails?
Check that the file matches a supported input, review the engine’s limitations and try a smaller representative file. If the engine cannot load, check its engine assets and browser requirements. The app reports failures without switching to a remote converter.
Continue with your output
These tools accept this tool’s output format. Each step has its own settings and fidelity limits.
- JSON to CSV
Convert JSON locally with an explicit structured-data mapping.
- JSON to TSV
Convert JSON locally with an explicit structured-data mapping.
- JSON to YAML
Convert JSON locally with an explicit structured-data mapping.
- JSON to XML
Convert JSON locally with an explicit structured-data mapping.
- JSON to SQLite database
Create a portable, single-table SQLite database from JSON records.
- JSON to JSON Lines
Write a JSON array of records as one compact object per line for data pipelines.
More data tools
- Inspect PostgreSQL SQL backup
List table names, columns and row counts from a PostgreSQL plain SQL COPY dump.
- PostgreSQL backup table to CSV
Extract one table from a PostgreSQL plain SQL COPY dump as CSV.
- CSV to JSON
Convert CSV locally with an explicit structured-data mapping.
- CSV to TSV
Convert CSV locally with an explicit structured-data mapping.
- CSV to YAML
Convert CSV locally with an explicit structured-data mapping.
- CSV to XML
Convert CSV locally with an explicit structured-data mapping.