HeidiSQL
HeidiSQL 12.20 is a lightweight graphical database client for MariaDB, MySQL, Microsoft SQL Server, PostgreSQL, SQLite, Interbase and Firebird. It provides data browsing, SQL editing, structure changes, import, export and session management.
What HeidiSQL provides
HeidiSQL 12.20 is a graphical client for browsing database objects, writing SQL, editing limited data and exporting selected structures or results. It supports several engines, but SQL dialects, drivers, permissions and backup mechanisms differ. A convenient grid does not make a destructive statement safer.
Sessions and production boundaries
A database client can perform every operation allowed by the current account. Use a read-only test account first, separate production sessions visually, verify the host, port, database, character set and timezone, and prefer trusted TLS or a controlled tunnel. Do not save credentials in shared configuration or screenshots.
Export and recovery
A grid export is not automatically a complete database backup. For important data, use the engine's native backup approach, define the scope and encoding, restore into an isolated test database and compare tables, key records and application connectivity before treating an export as recoverable. Review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave HeidiSQL to this cloud drive
Baidu Netdisk
Save HeidiSQL to this cloud drive
HeidiSQL 12.20 installation, read-only connection and export guide
Connect to a local or isolated test database first, inspect structure with a least-privilege account, review SQL before changes and validate a small export in an empty database.
Before you start
- Prepare the database type, host, port, name and a least-privilege test account; use a VPN, controlled SSH jump host or TLS for remote sessions.
- Confirm driver and runtime requirements for the target platform, and keep a recoverable database backup before exporting or changing structure.
- Record character set, timezone, primary keys and available destination space before an import or export.
Installation steps
- 01
Choose the stable package
Use the Windows 12.20 installer or portable build, or the matching Linux or macOS package, and keep preview builds separate from stable sessions.
- 02
Create a least-privilege session
Select the correct database type, enter only the test credentials and verify certificates, hostnames and jump-host fingerprints instead of ignoring TLS errors.
- 03
Review client behavior
Disable unnecessary telemetry or automatic actions, set query timeouts and delete confirmations, and use a visible read-only production session.
Quick start
- 01
Read structure and a small result set
Inspect tables, views, indexes and field types, then run a limited read-only query and confirm the target server, database and timezone.
- 02
Save and review SQL
Store queries as versioned scripts, preview affected rows inside a transaction and avoid unconditional bulk pastes into a production grid.
- 03
Make a narrow export
Select the required tables or results, choose encoding and whether structure or drop statements are included, then restore into an empty test database.
Usage tips
- Deletion, truncation, schema changes and cross-server exports remain constrained by the account permissions; the GUI does not reduce SQL risk.
- SQLite is a local file and should be snapshotted before editing; network databases should use native backup mechanisms for recovery.
- Remove passwords, private hostnames and customer database names from logs, screenshots and shared session files.
Troubleshooting and uninstall
Why does the connection time out or fail TLS?
Check that the database listens, the network and port are reachable, the jump host is correct, the certificate matches and the account is allowed from that source. Verify with the native client before changing security checks.
Why are characters corrupted after import?
Stop writing, compare server, database, table, connection and file encoding, and test a small sample in an empty database while keeping the original file.
- Export needed queries and notesKeep SQL scripts and credential-free session notes, confirm the database backup restores and avoid archiving passwords with ordinary configuration.
- Remove the client and local sessionsUninstall the application or remove the portable directory, clean sessions, logs, temporary exports and jump-host settings, and retire credentials created only for this client.
Frequently asked questions
Does HeidiSQL only support MySQL?
No. It also supports MariaDB, Microsoft SQL Server, PostgreSQL, SQLite, Interbase and Firebird, although drivers, structure editors and advanced features differ by engine.
Is the 13 preview suitable for production?
12.20 is the stable baseline while 13 is a newer-codebase preview. Keep it separate and test against a disposable database before considering a production session.
Is a HeidiSQL export a full backup?
Not automatically. Define the export scope and restore it into an isolated database, then compare schema, important records, encoding and application behavior.