SQL Database Viewer Online - View SQL Files & Database Tables

Upload and analyze SQL files online. Explore database tables, records, columns, relationships and ER diagrams directly in your browser.

Files never leave your device
Back to Tools
This tool is being ported to the new interface and will be back shortly.
  1. Drag and drop a .sql dump onto the upload area, or browse for one on your device — MySQL, PostgreSQL, and SQLite dumps are all supported.
  2. The tool automatically detects the SQL dialect from the file's contents (not just its extension) and parses it in a background Web Worker, so the page never freezes even on large files.
  3. Browse the database overview for table, row, column, and relationship counts, then pick any table from the sidebar to inspect its Data, Structure, Indexes, and Relations.
  4. Search, filter, and sort records directly in the virtualized data grid, or switch to the ER Diagram tab to see every foreign key relationship laid out visually.
  5. Open the SQL Console to run read-only SELECT queries against the loaded data, and export any table or query result as CSV, JSON, or SQL.

All processing happens entirely in your browser. Your data never leaves your device.

Key Features

  • Automatic SQL dialect detection for MySQL, PostgreSQL, and SQLite dumps, with a manual override if detection is ambiguous
  • A real statement-aware parser (not regex) that handles quoted identifiers, escaped strings, comments, multi-statement files, and dialect-specific syntax like COPY … FROM stdin
  • Background Web Worker processing with a live progress bar, so multi-hundred-megabyte dumps never freeze the page — and can be cancelled mid-import
  • A virtualized, paginated data grid per table with column sort, resize, show/hide, per-column filters, free-text search, and copy/export
  • Full schema inspection: column types, nullability, defaults, primary/unique/foreign keys, auto-increment flags, and indexes
  • Automatic foreign-key relationship detection, including constraints declared separately via ALTER TABLE
  • An interactive, pannable/zoomable ER diagram with a minimap, table search, show/hide, and click-to-open navigation
  • A read-only SQL console with syntax highlighting, autocomplete, and query history for exploring the loaded data safely
  • Database-wide search across every loaded table, and CSV/JSON/SQL export for any table page or query result
  • Graceful handling of malformed or partially-unsupported SQL — the database still loads with a clear list of what was skipped

About SQL Database Viewer Online - View SQL Files

A SQL dump is a text file — usually produced by mysqldump, pg_dump, or the SQLite CLI — containing every CREATE TABLE, INSERT, and constraint statement needed to recreate a database from scratch. Opening one to actually understand its structure normally means spinning up a real database server and a desktop client like phpMyAdmin, TablePlus, or DBeaver.

ForgeKit's SQL Database Viewer skips that setup entirely. It parses the dump with a real statement tokenizer (not regular-expression guesswork), rebuilds the schema and data inside an in-browser SQLite engine (sql.js, compiled to WebAssembly), and renders the result as a proper database-management interface — table browser, schema inspector, foreign-key explorer, interactive ER diagram, and a SQL console — all running inside a Web Worker so the page stays responsive even on large files.

Because everything happens client-side, nothing about the database — table names, column values, customer records, credentials that might be sitting in seed data — is ever uploaded anywhere. The dump is read directly from disk into browser memory, parsed and queried locally, and discarded when you close the tab.

Frequently Asked Questions

No. The file is read directly in your browser and parsed inside a local Web Worker using sql.js (SQLite compiled to WebAssembly). Nothing about your database — schema or data — is ever sent over the network or stored on any server.

MySQL, PostgreSQL, and SQLite dumps are detected automatically from the file's actual syntax (ENGINE=, SERIAL, PRAGMA, and similar markers), not just the file extension. If detection is ambiguous, you can pick the dialect manually.

Yes. Parsing and loading run in a background Web Worker with a progress indicator, so the page stays responsive. Very large dumps are subject to a row-count safety cap to protect browser memory — you'll see a clear warning if that limit is reached.

Unsupported statements are skipped and listed in an import-warnings panel, but the rest of the database still loads normally. You can keep exploring every table that did parse successfully.

Yes, through the built-in SQL Console. Queries run entirely against the in-browser SQLite engine — there's no path to the filesystem, a shell, or any server, so it's safe to experiment with even an untrusted dump.

Yes. Any table page or query result can be exported as CSV, JSON, or SQL INSERT statements, generated entirely in your browser with no upload required.