Download Query Studio for Windows, macOS, Linux and Android

On Windows, the installer unless you cannot install software on the machine — then take the portable build, which runs from anywhere including a USB stick. On a Mac made from late 2020 onwards, Apple silicon; older Macs, Intel. On Linux, x86-64 unless you are on a Raspberry Pi or an ARM server. On Android, the single APK covers every device.

Because it is not signed with a code-signing certificate, which costs a few hundred a year for a tool that makes nothing. SmartScreen shows the warning on any unsigned installer regardless of what is in it. Click More info, then Run anyway. If you would rather verify first, every download here publishes its SHA-256 — compare it with certutil -hashfile <file> SHA256.

Almost certainly not. macOS quarantines anything downloaded from the internet that is not notarised, and reports it with that wording. Right-click the app in Finder and choose Open, which gives you an Open button the plain double-click does not, or run xattr -cr on the app once. Notarising requires a paid Apple developer account.

Extract the archive and run the binary inside it: tar -xzf QueryStudio-1.0.0-x64.tar.gz then ./QueryStudio-1.0.0-x64/query-studio. There is no install step and nothing is written outside that directory. An AppImage and a .deb are not built yet.

Android blocks installs from outside the Play Store until you allow it for the app doing the installing — usually your browser or file manager. The prompt appears the first time and points you at the right setting. The APK is signed, so once that is allowed it installs normally.

Because they are. All three were cross-compiled on a Windows machine, which is also the only platform the app has actually been launched on. The archives have been checked for structure — signatures, permissions, that the DuckDB engine is packaged — but that is not the same as knowing the app opens. They are published anyway because a build you can try beats a page that says coming soon, and because one report is all it takes to find out.

Open an issue on GitHub with your platform, the version, and what happened — a screenshot of the error is ideal. You can also use the contact page. There is no telemetry and no crash reporting in these apps, by design, so a report from you is the only way a problem on a platform I cannot test reaches me.

No. An iOS build has to be compiled with Xcode on a Mac and signed with a paid Apple developer account, and there is no way around either requirement. The browser version works in Safari on iPhone and iPad, and Add to Home Screen from the share menu gives you an icon that opens straight into it — the same engine, with the same roughly 900 MB ceiling an App Store build would have.

No, and the Android build cannot use one even in principle — it declares no internet permission at all, so the operating system would refuse the request. DuckDB and its WebAssembly assets ship inside every build rather than being fetched from a CDN. Install it, disconnect the machine, and everything still works.

There is nothing to uninstall — the browser version is just a page. The apps and the site are the same tool and do not share any state, since neither one stores anything. Use whichever is in front of you.

Download the new version and install it over the old one. There is no updater and no update check, which is a deliberate consequence of the apps having no network client at all. On Android, install the new APK over the existing one — it is signed with the same key, so it upgrades in place.

Yes. No account, no trial, no paid tier, no telemetry. It is MIT licensed and the source is on GitHub. Nothing about it is server-side, so it costs nothing to run and there is nothing to upgrade to.