Free SQL→ER diagram tool, runs in the browser, nothing uploaded

315 points - today at 3:43 AM

Source

Comments

michaelmior today at 10:42 AM
The tool looks very cool! But IMO you can't get an ER diagram from SQL since entities are fundamentally different from tables. They are certainly very similar, but SQL alone doesn't give you enough information to create an ER diagram.

That's not to say that the tool is useless or that diagrams of this sort are unhelpful. I'll admit I'm being pedantic and others will probably disagree.

written-beyond today at 5:54 AM
100/10 for mobile usability. Panning, Zooming, selecting and moving was so seamless I thought I was tripping out.
robhati today at 5:18 AM
It's a small too nothing great I just figured others might find it useful too. I kept finding myself needing to visualize database schemas, but most tools had the same problems: paywalls, mandatory signups, or sending your SQL to someone else's server.

No backend, no accounts, no data leaving your machine.

A few implementation details that were fun:

* Built on <canvas> instead of DOM/SVG. Tables are rasterized into cached bitmaps with viewport culling, which keeps things smooth even with hundreds of tables on screen.

* The SQL parser tracks source spans for every token. That lets edits stay surgical so a rename a table and only the relevant identifier (and its references) change while comments and formatting remain untouched.

* The URL contains the entire schema. Sharing simply serializes the schema into the URL itself, so there's no backend, no stored state, and no account required.

* I also experimented with a Rust/WASM version because why not? but the parser was ~37% slower because the JS↔WASM boundary cost outweighed the compute savings but The O(n^2) overlap-resolution pass was about 2.2x faster though * In the end I stuck with plain JavaScript. No framework ~32KB gzipped

throwatdem12311 today at 1:14 PM
Reminds me of: https://explain.dalibo.com/

For visualizing query plans. One of the most useful tools for optimizing sql queries I’ve ever used.

Just make sure to download the fully offline v2 version at the bottom if you want to use it with anything sensitive.

corkybeta today at 5:50 AM
Could we have the option of straight lines and 90 degree angles? I’ve never really liked the bendy ones. Looks cool, good job!
mingodad today at 1:21 PM
I'm using https://github.com/ondras/wwwsqldesigner and I think that's worth taking it in account for comparison.
petilon today at 1:42 PM
Nice, but there is no LICENSE file in the github: https://github.com/royalbhati/sqltoerdiagram
Igor_Wiwi today at 10:06 AM
btw did you know that ER diagrams are supported by Mermaid diagrams: https://mdview.io/mermaid?example=working-er It's not that pretty as in your app, but it does the work
hoofedear today at 12:01 PM
This is cool! I made something similar a little while ago that I’ve been touching up here and there. You can’t export to any SQL but I just wanted a tool I can use to diagram tables: https://datagram.studio

Edit: should clarify mine is also free! It’s quite specific to my needs but I’m happy with it

CodesInChaos today at 12:42 PM
Is there a way to hide connections to specific tables? Or alternatively filter out foreign keys by name.

For example in a multi-tenant application 90% of tables will link to the tenant table, but those links add little value to the viewer, so hiding these would be nice.

osrec today at 12:02 PM
Have only had a quick look at it, but it looks very nicely done! Out of interest, did you use AI to assist with development? If yes, what percentage of the code would you say is AI generated vs conventional?
ktzar today at 9:37 AM
Such an old problem solved very elegantly. Congrats. Remember the days of MySQL Workbench and how clunky it was.
WhyIsItAlwaysHN today at 7:08 AM
Maybe you can support schemas in more dialects by using a similar approach to a little tool I made: sqlscope.netlify.app

Basically integrate sqlglot to translate the schema between dialects and then use a base dialect for generating the schema.

The two tools seem complementary and you seem to be a better designer, so it would be nice to see it all together

flojo today at 12:30 PM
Great tool Thanks for this. Please consider "keeping it going"
swatiahuja today at 12:05 PM
good work, I was really in need of something like this to visualise my schemas
rognjen today at 8:04 AM
There's also Azimutt: https://azimutt.app/gallery
clutter55561 today at 11:19 AM
Great stuff, well done and super useful!
mehtablr today at 1:54 PM
Its there already as dbdiagram, what's new?
ahmdnassir1 today at 12:15 PM
This is cool! People actually need sthng like this.
agentic_vector today at 5:48 AM
I was looking for it, thanks! Great work!
henryecw today at 11:01 AM
Looks great, I’ll use this next week :p
_f1ou today at 5:00 AM
The GitHub link takes you to the front page of GitHub instead of the actual project.
John_Kwick today at 5:54 AM
Okay thats pretty cool. Nice job!
linzhangrun today at 9:54 AM
nice!
robhati today at 3:45 AM
I kept finding myself needing to visualize database schemas, but most tools had the same problems: paywalls, mandatory signups, or sending your SQL to someone else's server.

So I ended up building my own.

You paste in your CREATE TABLE statements and it generates an interactive ER diagram right in the browser. You can drag tables around, auto arrange the layout, edit table/column names directly on the canvas (it rewrites the SQL for you), add notes and group boxes, and export as PNG or SVG.

No backend, no accounts, no data leaving your machine.

A few implementation details that were fun:

* Built on <canvas> instead of DOM/SVG. Tables are rasterized into cached bitmaps with viewport culling, which keeps things smooth even with hundreds of tables on screen.

* The SQL parser tracks source spans for every token. That lets edits stay surgical so a rename a table and only the relevant identifier (and its references) change while comments and formatting remain untouched.

* The URL contains the entire schema. Sharing simply serializes the schema into the URL itself, so there's no backend, no stored state, and no account required.

* I also experimented with a Rust/WASM version because why not? but the parser was ~37% slower because the JS↔WASM boundary cost outweighed the compute savings but The O(n^2) overlap-resolution pass was about 2.2x faster though * In the end I stuck with plain JavaScript. No framework ~32KB gzipped

It's a small too nothing great I just figured others might find it useful too.

hitoshi1964 today at 11:38 AM
[flagged]
throwaway613746 today at 1:25 PM
[dead]
deleted today at 5:08 AM