Back to all posts

The Best MySQL GUI Client: Free Options and What a Paid Licence Adds

Which MySQL GUI clients are free, what they leave out, and what a paid DbSchema licence adds and costs over three years.

On this page

You want a MySQL GUI client: a desktop program to run queries, edit rows and look at your tables without a command line. Free clients do this well, and every list names a dozen of them.

Short answer

Try DbSchema first: its free Community Edition connects to MySQL, draws your tables as a diagram and runs SQL. DbSchema Pro costs 294 USD once per developer. It saves your design as a file that you review in Git and deploy after a compare.

  • Every DbSchema download starts with 15 days of all features, without registration.
  • After the trial, the DbSchema Community Edition stays free for any use.
  • DbSchema Pro keeps your MySQL design in a model file and in Git, and deploys it after a compare.

A SQL client shows you the database, DbSchema gives you the model. The model is a design you change, review and deploy when you are ready.

What DbSchema adds to a MySQL client

DbSchema connects, runs SQL and edits rows like any MySQL client. On top of that, it keeps a design model.

The model is DbSchema's own copy of your schema, saved as a .dbs file. The schema is the set of tables, columns and keys in a database.

  • See how your tables connect. In the free Community Edition, DbSchema reverse-engineers MySQL: it reads the existing tables and draws them as an ER diagram (Connect to Database). An ER diagram shows each table as a box and each foreign key as a line. A foreign key is a column that points to a row in another table.
  • Change the design without touching the server. Choose Database → Offline (connect later), and your edits stay in the model. MySQL doesn't change until you decide. Saving the model with File → Save Model to File needs DbSchema Pro (Schema Synchronization).
  • Review every change like code. Git is a version control system: it keeps every version of a file and who changed it. DbSchema has Git built in, under File → Git Collaboration. The .dbs file is plain XML text, so Git shows what changed between two versions (DbSchema Pro, Git Collaboration).
  • Deploy only what you checked. Schema synchronization compares the model with the live MySQL database and lists every difference. DbSchema then writes the migration script, the SQL statements that bring the database up to date. It shows the script before anything runs (DbSchema Pro, Schema Synchronization).
  • Query and browse without typing joins. A join combines the rows of two tables, such as customers and their orders. The Query Builder builds the join from the foreign key while you tick columns. The Data Explorer follows the same key from a customer to that customer's orders (DbSchema Pro).
Two ways to change a MySQL table. In a SQL client, the ALTER TABLE you run changes the live database at once. In DbSchema, the change waits in the model file, goes through Git review and a compare, and only then runs on MySQL as a migration script
Figure 1A SQL client changes MySQL the moment you run a statement. DbSchema keeps the change in the model until you have reviewed it.

The steps are under Keep a MySQL design in Git with DbSchema.

What the free MySQL clients leave out

Three free clients come up on every list. Each one does its main job well.

MySQL Workbench Community Edition is free and open source. Open source means anyone may read and change the program's code.

Workbench runs SQL and models a schema graphically. It can reverse and forward engineer between a schema and a live database. Forward engineering is the opposite of reverse-engineering: it creates the tables from the model.

DBeaver Community is free as well and runs SQL on MySQL. HeidiSQL is free, open source and has builds for Windows, Linux and macOS.

The gaps show once the work moves past running queries:

Free clientWhat it leaves out
DbSchema CommunityModel file, Git, documentation, synchronization (DbSchema Pro)
MySQL WorkbenchOther engines; a visual query designer (no plans); merging .mwb models in Git (binary)
DBeaver CommunitySchema compare is in the Enterprise and Ultimate editions only; no documentation generator (open request)
HeidiSQLER diagrams: the request was closed as not planned

For teams, Workbench saves its model as a binary .mwb file, which Git can't merge. Merging means combining two people's edits to the same file. DbSchema's .dbs file is text, so Git can merge it.

DbSchema Community already covers what HeidiSQL lacks: it draws the MySQL schema as a diagram you can rearrange. It also connects to PostgreSQL, SQL Server, MongoDB and other engines in the same window. MySQL Workbench alternatives for multi-engine teams covers that switch.

Keep a MySQL design in Git with DbSchema

You need DbSchema Pro or the trial, a MySQL login and a Git repository. A repository is a folder that Git tracks, usually shared on a server such as GitHub or GitLab.

  1. Choose File → New Model, keep Connect to Database selected, and click MySQL.
  2. Choose New Connection and press Connect to MySQL. Fill in the host, the port, the user and the database, then press Connect.
  3. In Reverse Engineer the Database, tick your schema and press Import. Connecting and importing only read from MySQL and change nothing.
  4. Choose File → Git Collaboration. The first time, the dialog says No repository found.
  5. Choose More → Clone. Paste the repository address into GIT URL, pick an empty folder in Into Folder (empty), and press Clone.
  6. Save the model into that folder with File → Save Model to File.
  7. Open File → Git Collaboration again. Under Uncommitted changes, tick the .dbs file, type a Commit message and press Commit.
  8. Press Push to share your commits.

DbSchema downloads the JDBC driver at the first connect. A JDBC driver is a small Java library that lets DbSchema talk to MySQL.

A commit is a saved version of your changes, with a message. Push sends your commits to the shared repository, so your team gets them.

The DbSchema Git dialog for the model shop.dbs, with commits by Ana Lopez and Ben Carter, a merge, the Pull, Push and Model History buttons, and Everything is up to date
Figure 2The Git dialog lists every commit to the model file, with its author and message.

From then on, your teammates press Check for incoming changes, then Pull, which gets your commits. Reload Project then opens the new version. Model History lists each commit with the tables it changed.

The DbSchema loop for MySQL in five steps: reverse-engineer MySQL into the model, edit offline, commit and push the .dbs file to Git, compare the model with MySQL, and run the reviewed migration script
Figure 3The model moves through Git first. MySQL changes only at the last step, after the compare.

To bring a reviewed change into MySQL, connect again. Choose Compare, then decide difference by difference.

On each row, click the side that wins: the model or the database. Then press Generate SQL script to save the script, or Commit in the database to run it on MySQL. This is not a Git commit.

What the paid MySQL clients cost over three years

The table counts one developer for commercial use, with updates for all three years. We read every price on the vendor's own page on 15 November 2026.

A perpetual licence is paid once and keeps working. Paying for later updates is optional. A subscription is paid every year, or access ends.

ToolLicenceFirst yearThree years with updates
DbSchema ProPerpetual, per developer, two computers294 USD444 USD
TablePlus BasicPerpetual, one device99 USD217 USD
DBeaver LiteYearly subscription113 USD339 USD
DBeaver EnterpriseYearly subscription255 USD765 USD
DataGrip, organizationsYearly subscription259 EUR777 EUR

DbSchema Pro includes the first year of updates.

Each later year of updates, meaning new versions, costs 75 USD and is optional. So 444 USD is 294 USD plus two years at 75 USD. If you stop renewing, DbSchema Pro keeps working with the versions you have.

DBeaver blocks access after the subscription ends. Over three years, DbSchema Pro costs less than DBeaver Enterprise, the DBeaver edition with schema compare. It also costs less than DataGrip for organizations, which JetBrains showed in euros when we read the page.

TablePlus Basic costs less and covers one device. A DbSchema licence covers two computers, used one at a time. If you pay for it yourself, the Personal licence of DbSchema Pro costs 196 USD once.

The model file, Git, schema synchronization, the query builder and HTML5 documentation need DbSchema Pro. The purchase page lists every edition.

Download DbSchema, connect it to your MySQL database and try every feature free for 15 days. After the trial, the Community Edition keeps connecting, drawing diagrams and running SQL, for any use.

Sources

  1. DbSchema: Connect to Database
  2. DbSchema: Schema Synchronization
  3. DbSchema: Git Collaboration
  4. DbSchema: Query Builder
  5. DbSchema: Data Explorer
  6. MySQL Workbench manual: General Information
  7. HeidiSQL
  8. MySQL bug 55894: visual query designer
  9. MySQL bug 83076: merging .mwb files
  10. DBeaver documentation: Schema compare
  11. DBeaver issue 5158: documentation tool
  12. HeidiSQL issue 2117: ER diagrams
  13. DbSchema: Pricing
  14. DBeaver: License types
  15. DBeaver: Buy
  16. JetBrains: DataGrip pricing
  17. TablePlus: Pricing
  18. DbSchema: Schema Documentation

Query MySQL free, and keep the design in Git when you need it

The DbSchema Community Edition connects to MySQL, draws the schema and runs SQL, free for any use. DbSchema Pro adds the model file, Git, schema synchronization, the query builder and documentation.