Data dictionary generator

ErdDocs generates a data dictionary from a SQL dump, a Prisma schema or framework models: every table, column, type, default, index and relationship in one reference document, saved as a PDF from the browser’s print dialog, with an interactive ER diagram beside it. No signup, no install; the schema is parsed in your browser and never uploaded.

Your schema

CREATE TABLE customers (
    id          bigserial PRIMARY KEY,
    email       varchar(255) NOT NULL UNIQUE,
    full_name   varchar(120),
    created_at  timestamptz  NOT NULL DEFAULT now()
);
COMMENT ON TABLE customers IS 'Registered buyers; one row per person';
COMMENT ON COLUMN customers.email IS 'Login identity, unique across the shop';

CREATE TABLE products (
    id        bigserial     PRIMARY KEY,
    sku       varchar(40)   NOT NULL UNIQUE,
    title     varchar(200)  NOT NULL,
    price     numeric(10,2) NOT NULL,
    stock     int           NOT NULL DEFAULT 0
);
COMMENT ON TABLE products IS 'Catalog; soft-deleted items keep their SKU';
COMMENT ON COLUMN products.stock IS 'On-hand quantity, updated by the warehouse feed';

CREATE TABLE orders (
    id           bigserial     PRIMARY KEY,
    customer_id  bigint        NOT NULL REFERENCES customers(id),
    status       varchar(20)   NOT NULL DEFAULT 'pending',
    total        numeric(10,2) NOT NULL,
    placed_at    timestamptz   NOT NULL DEFAULT now()
);
COMMENT ON COLUMN orders.status IS 'pending -> paid -> shipped -> done, or cancelled';

CREATE TABLE order_items (
    order_id    bigint        NOT NULL REFERENCES orders(id),
    product_id  bigint        NOT NULL REFERENCES products(id),
    qty         int           NOT NULL,
    unit_price  numeric(10,2) NOT NULL,
    PRIMARY KEY (order_id, product_id)
);
COMMENT ON TABLE order_items IS 'Line items; price is frozen at purchase time';

CREATE TABLE shipments (
    id         bigserial   PRIMARY KEY,
    order_id   bigint      NOT NULL REFERENCES orders(id),
    carrier    varchar(60) NOT NULL,
    tracking   varchar(80),
    shipped_at timestamptz
);

CREATE INDEX idx_orders_customer ON orders(customer_id);
CREATE INDEX idx_shipments_order ON shipments(order_id);

CREATE TABLE customers (
    id          bigserial PRIMARY KEY,
    email       varchar(255) NOT NULL UNIQUE,
    full_name   varchar(120),
    created_at  timestamptz  NOT NULL DEFAULT now()
);
COMMENT ON TABLE customers IS 'Registered buyers; one row per person';
COMMENT ON COLUMN customers.email IS 'Login identity, unique across the shop';

CREATE TABLE products (
    id        bigserial     PRIMARY KEY,
    sku       varchar(40)   NOT NULL UNIQUE,
    title     varchar(200)  NOT NULL,
    price     numeric(10,2) NOT NULL,
    stock     int           NOT NULL DEFAULT 0
);
COMMENT ON TABLE products IS 'Catalog; soft-deleted items keep their SKU';
COMMENT ON COLUMN products.stock IS 'On-hand quantity, updated by the warehouse feed';

CREATE TABLE orders (
    id           bigserial     PRIMARY KEY,
    customer_id  bigint        NOT NULL REFERENCES customers(id),
    status       varchar(20)   NOT NULL DEFAULT 'pending',
    total        numeric(10,2) NOT NULL,
    placed_at    timestamptz   NOT NULL DEFAULT now()
);
COMMENT ON COLUMN orders.status IS 'pending -> paid -> shipped -> done, or cancelled';

CREATE TABLE order_items (
    order_id    bigint        NOT NULL REFERENCES orders(id),
    product_id  bigint        NOT NULL REFERENCES products(id),
    qty         int           NOT NULL,
    unit_price  numeric(10,2) NOT NULL,
    PRIMARY KEY (order_id, product_id)
);
COMMENT ON TABLE order_items IS 'Line items; price is frozen at purchase time';

CREATE TABLE shipments (
    id         bigserial   PRIMARY KEY,
    order_id   bigint      NOT NULL REFERENCES orders(id),
    carrier    varchar(60) NOT NULL,
    tracking   varchar(80),
    shipped_at timestamptz
);

CREATE INDEX idx_orders_customer ON orders(customer_id);
CREATE INDEX idx_shipments_order ON shipments(order_id);

Your diagram appears here.

The example above carries schema comments — that is why its dictionary has a Description column. Paste your own dump to see yours.

From database to dictionary in three steps

01Export the schema: pg_dump --schema-only mydb > schema.sql for PostgreSQL, mysqldump --no-data mydb > schema.sql for MySQL, or take your Prisma schema.prisma as it is.
02Paste it above or drop the file onto the panel — the dictionary appears as the schema is read.
03Click Save as PDF — your browser’s print dialog produces the document. It never touches a server either.

Descriptions come from your schema

A data dictionary is only as good as its descriptions, and databases already have a place for them — most teams just never see it rendered:

PostgreSQL — COMMENT ON TABLE orders IS '…' and COMMENT ON COLUMN orders.status IS '…'; pg_dump exports them with the schema automatically.
MySQL — inline COMMENT '…' on columns and tables in CREATE TABLE; mysqldump keeps them.
Prisma — /// documentation comments above models and fields land in the dictionary as descriptions.

Everything else is read from the DDL itself: types as written, nullability, defaults, keys, indexes, partitions folded under their parent table — and when a dump declares no foreign keys at all (Rails and Django rarely do), relationships are recovered from column naming and marked as such, so an auditor can always tell declared keys from inferred ones.

Who asks for one

Audits and compliance — “send us the data dictionary” is a standard request; ErdDocs answers it from a pasted schema dump in minutes, while assembling one by hand against a live database takes days.
Client handover — agencies close projects with documentation; ErdDocs produces that deliverable as a document the client can print and keep.
Onboarding — a new engineer reads one document instead of interrogating information_schema table by table.

FAQ

What does the generated data dictionary contain?

ErdDocs describes every table: its columns with data types exactly as declared, nullability, default values, primary and foreign keys with the columns they point at, unique constraints, indexes, and both directions of every relationship. Table and column comments from the schema become descriptions. Partitioned tables are listed once, with their partitions named under the parent.

How do I generate a data dictionary from an existing database?

Export the schema as SQL — pg_dump --schema-only for PostgreSQL, mysqldump --no-data for MySQL — then paste the file above, and switch to the Data Dictionary view. Printing the document with your browser produces the PDF. Nothing is installed and the SQL never leaves your machine.

How do descriptions get into the dictionary?

From the schema itself: PostgreSQL COMMENT ON TABLE and COMMENT ON COLUMN statements, MySQL inline COMMENT 'text' clauses, and Prisma /// documentation comments all land in the Description column. Where a schema carries no comments, ErdDocs leaves the Description column out entirely rather than printing it empty, so the document never shows scaffolding you would have to fill in.

Is it free?

The diagram renders up to 25 tables free, and the dictionary describes the three most-connected tables in full, with the tables that follow standing as named outlines in the places they would occupy and any remainder counted — enough to see the exact document you would get. One payment of $9 unlocks the complete dictionary and the full diagram forever: no subscription, no account.

Does my schema get uploaded anywhere?

No. Parsing, the diagram and the dictionary all run inside your browser, and the PDF is produced by your browser printing the page. The schema never reaches a server — there is nothing to upload it to.

MySQL data dictionary generator — mysqldump specifics, inline COMMENT syntax.
PostgreSQL data dictionary generator — pg_dump idioms, COMMENT ON, partitions.
Data dictionary template — the seven columns, a CSV to download, and how to fill each one by hand.
Database documentation tools — the landscape: open source generators, code-first, platforms.
Dataedo alternative — when a document is enough and a platform is too much.
SQL to ER diagram — the same tool, opened on the diagram view.
Agent Link API — link any schema to a live diagram and dictionary from a README or an AI answer.