There is no shortage of free ERD tools, but "free" means something different for every online ER diagram maker — some cap the number of diagrams, some cap tables per diagram, and some lock private diagrams behind payment.
The table below compares the free tiers of five browser-based ERD tools as checked in August 2026. They differ in diagram visibility, table limits and export conditions even though none requires a desktop installation.
Three things to check before you choose
Do you need private diagrams? A company schema is internal information by itself. If a free plan is public-only, rule it out for work before you start.
Do you need SQL in and out? If a database already exists, whether the tool imports DDL (and exports it back) decides how much typing you do. A tool that only draws pictures ends at pictures.
Where does the limit bite? A cap on diagram count can be managed by deleting old ones. A cap on tables per diagram has no workaround once your schema outgrows it.
The five tools at a glance
| Tool | Free tier | Editing style | Notes |
|---|---|---|---|
| dbdiagram.io | Up to 10 public diagrams | DBML code | No table cap, SQL import/export, PNG/PDF/SVG output |
| drawSQL | No account: 20 tables, local storage / free account: public diagrams, 15 tables each | GUI | SQL import, sharing and embedding |
| ChartDB | Cloud free: 2 private diagrams · 10 tables each | GUI | Open source; no table cap when self-hosted |
| ERDCloud | Free to use | GUI | Real-time co-editing, Korean service |
| WorksCove ERD | 3 projects · 40 tables per project | GUI | SQL round-trip for 4 DBMS, version history |
Limits and prices change often. Check each tool's official pricing page before you commit — this table reflects what we verified in August 2026. One more shared trait: all five draw relationships in crow's foot (IE) notation, so learning the symbols once carries across every tool.
A closer look at each
dbdiagram.io: You write tables in a small language called DBML instead of dragging boxes. It looks like this:
Table members {
id bigint [pk, increment]
email varchar(255) [unique, not null]
nickname varchar(50) [not null]
}If you're comfortable in code this is genuinely faster, and because the source is text, diagrams can live in git, go through code review, and show schema changes as diffs — something GUI tools can't offer. dbdiagram's own community also notes there is no table-count limit even on free, so a single large schema managed as code works fine.
drawSQL: Its no-account canvas supports up to 20 tables and keeps the draft in browser storage. A free account saves diagrams permanently, but those diagrams are public and limited to 15 tables each. Private storage, version history, and real-time collaboration on an account require a paid plan.
ChartDB: The free cloud plan allows two private diagrams with ten tables each. The open-source edition has no table cap when self-hosted, but it does not include the cloud service's built-in accounts, sharing, and real-time collaboration as the same package. It fits teams that can operate the server and need to control where schema data lives.
ERDCloud: A Korean service widely used there, mainly because real-time co-editing costs nothing — which is why it's a common choice for student team projects and study groups. It exports images, Excel and SQL, which makes it an easy start for a team on no budget. The ERDCloud tutorial covers the path from sign-up through export.
WorksCove ERD: This is our tool, so we'll skip the praise and just state the free tier precisely. Three projects, 40 tables per project. For scale: the forum example above is 4 tables, so the free ceiling is ten times that — roughly the full schema of an early-stage service. DDL import and export cover MySQL, PostgreSQL, Oracle and SQL Server, and table specifications, version history and an AI assistant (50K tokens per month) are all included. Team collaboration is paid.
Three tips for getting the most out of a free plan
Whichever tool you pick, a few things are worth knowing up front if you plan to stay on the free tier for a while.
The table cap. When a schema outgrows the limit, the first idea is usually to split it across several diagrams. Resist it — the moment you split, the FK lines between the parts disappear from view, and "seeing relationships at a glance" was the whole point of an ERD. If you've hit the cap, moving to a tool with more headroom beats fragmenting the design.
Public diagrams. A public diagram is visible to anyone with the URL, and can end up in search results. If table names contain your company or product name, it's that much easier to find. For real schemas, confirm private diagrams are possible first, and keep public-only free plans for practice schemas.
Export gates. Sometimes drawing is free but getting the result out (high-resolution images, SQL, documents) is not. A diagram isn't finished until it's shared or submitted, so check that the format you ultimately need to produce is inside the free tier before you invest hours in a tool.
Switching tools in practice
If you've decided to move, the procedure is short: export SQL (DDL) from the old tool, import it into the new one. DDL is the common language.
Three things to keep in mind before you start:
- Match the dialect. If you exported MySQL, import as MySQL. If the new tool supports several DBMS, this is just a dropdown to get right.
- Layout doesn't travel. DDL carries no positions or colors, so expect to re-arrange with auto-layout after the move. If you had a hand-tuned layout, that part is redone.
- Check whether comments survive. Not every export includes COMMENTs. If you've been keeping logical names and descriptions in comments, open the exported DDL and confirm they are there before you commit to the move.
After the move, compare table and FK counts against the original, and keep the original file around for a while. The import itself is the same exercise as in How to Draw an ERD, and if you want to turn the moved schema straight into documentation, that path is covered in How to Write a Table Specification.
Which one for which situation
- You want diagrams managed as code → dbdiagram.io. It fits review-and-version workflows best.
- You can run your own install → ChartDB. Open source, and your data stays yours.
- A team needs to draw together on no budget → ERDCloud. Real-time co-editing is included without payment.
- The work is small and fine to be public → drawSQL. The clean look makes coursework presentable.
- You want to import DDL, draw, and continue into specs → WorksCove ERD. The 4-DBMS round-trip and the 40-table free ceiling are built for that flow.
FAQ
Which free ERD tool is the best?
There is no single best option. Choose dbdiagram for diagrams as code, ChartDB for self-hosting, or ERDCloud when free simultaneous editing matters. Compare privacy, table limits, and required export formats before deciding.
Can I keep using a free plan for real work?
It depends on schema size and the deliverables you need. Some free tiers stop at 10-20 tables per diagram, so a schema with dozens of tables needs a higher-cap tool or a self-hosted option. Check privacy, export, and real-time collaboration limits as well.
Is it safe to draw my company's schema in a free tool?
Check first whether the free plan is public-diagrams-only — some are. Table and column names alone reveal how a service works, so treat the schema itself as internal information.
Why aren't desktop tools like MySQL Workbench or DBeaver on the list?
This comparison covers only tools you can start in a browser without installing anything. Desktop tools differ in setup and sharing, so putting them in the same table would blur the criteria. MySQL Workbench and A5:SQL Mk-2 each have a guide of their own.
How do I switch from one tool to another?
Export SQL (DDL) from the old tool and import it into the new one. DDL is the common language between these tools, so as long as both sides support SQL in and out, the cost of moving is small.
Compare privacy, SQL round-trip support and the point where each limit applies before creating a work diagram. Those three conditions usually narrow the list without moving a schema between several tools first.