Frequently Asked Questions
Everything you need to know about our browser-only architecture, privacy guarantees, and database tooling.
Privacy & Security Guarantees
How can I independently verify that SQLParity does not upload my queries or schemas?
Open your browser’s Developer Tools (F12 or right-click → Inspect), click the Network tab, and clear the log. Then paste queries into any tool, convert dialects, or run SQL on a CSV in the scratchpad. Notice that zero outgoing network requests occur. Everything computes directly in your computer’s RAM.
What is Content Security Policy and how does connect-src "self" protect my team?
A Content Security Policy (CSP) is an HTTP security header sent to your browser that restricts what resources the page is allowed to load. SQLParity sets connect-src "self", which strictly instructs the browser to block and throw a hard error on any attempt by any script to send data to an external API or remote origin.
I saw a network request when clicking "Download Excel". Is my data uploaded?
No. To keep initial page loads ultra-fast, SQLParity uses code-splitting (lazy loading). When you click the Excel download button for the first time, your browser downloads the ~20 KB JavaScript module (write-excel-file) required to assemble spreadsheets locally. You are downloading code into your browser, not uploading your data. You can verify this by checking the request payload—it contains zero data.
Are my settings, queries, or history saved on a server?
No. SQLParity has no backend database, no login system, and no user accounts. Basic UI preferences (like your preferred SQL dialect) are kept in your browser’s local storage only and never transmitted anywhere.
Features & Technical Architecture
How does the DuckDB Scratchpad work inside the browser?
DuckDB is compiled into WebAssembly (WASM). When you drag and drop a Parquet, CSV, or TSV file, the browser File API reads the file directly into DuckDB’s in-memory WASM engine, allowing you to run full analytical SQL queries locally at native speeds.
What is the file size limit for Parquet or CSV files in the scratchpad?
Because DuckDB runs inside your browser’s WebAssembly memory space, performance depends on your computer’s available RAM. Files up to a few hundred megabytes (and hundreds of thousands of rows) typically query in seconds.
Which SQL dialects are supported across the tools?
SQLParity supports 16 major database engines: PostgreSQL, MySQL, SQLite, SQL Server (T-SQL), Oracle, MariaDB, Snowflake, Google BigQuery, Amazon Redshift, Trino / Athena, Apache Spark SQL, Apache Hive, ClickHouse, DuckDB, IBM Db2, and Standard SQL.
Does SQLParity work offline without an active internet connection?
Yes. After the initial page load has loaded the assets into your browser cache, the core parsing, formatting, diffing, and DuckDB querying operate completely offline.
Licensing, Commercial Use & Open Source
Is SQLParity free to use for commercial and enterprise database migrations?
Yes. SQLParity is 100% free to use for personal, commercial, and enterprise workflows. There are no paid tiers or feature paywalls.
What open source license is SQLParity released under?
SQLParity is open source and licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). The full source code is publicly accessible on GitHub.
How can I report a syntax edge case or request support for another database engine?
You can open an issue or pull request directly on our GitHub repository at github.com/bhardwajtulsiram/sqlparity.
Have a question or edge case not covered here?
Open an issue or ask the community directly on GitHub.