SQLite ER Diagram Generator

Create the diagram

Open the SQLite database in the viewer.
Select ER diagram in the table sidebar.
Use Fit to bring all entities into the dialog viewport.
Inspect each entity’s column names, SQLite data types and key markers.

The relationship lines are derived from declared SQLite foreign keys. If a logical relationship is not defined with a foreign-key constraint, a schema reader cannot identify it reliably from column names alone.

How to read the result

PK identifies a primary-key column used to uniquely address a row.
FK identifies a column that references a key in another table.
Column types show the declared SQLite type. SQLite’s flexible type system means stored values can sometimes vary from that declaration.
Connecting edges show the referenced and referencing entities.

A diagram is most useful when the database declares primary and foreign keys consistently. Missing lines often indicate missing constraints rather than a rendering problem.

Export the schema

After reviewing the diagram, export its schema as SQL DDL, DBML, Mermaid or GraphQL SDL. SQL DDL is closest to the original database definition. DBML and Mermaid are useful for documentation. GraphQL SDL is a starting point for an API model and may need application-specific adjustments.

Useful review questions

Look for tables without primary keys, foreign keys pointing to unexpected entities, inconsistent naming, nullable columns that should be required, and junction tables that represent many-to-many relationships. These checks help when inheriting an application database or planning a migration.