100% free · no signup

Table names that don't stink —
plural? singular? you decide. We generate.

Spin up database table names for schemas, migrations and mock data. Flip between plural and singular, pick your case style, stamp on prefixes or suffixes, or mint join-table pairs. Everything runs 100% in your browser — nothing leaves your device.

100% in your browser no signup, no tracking copy or download .txt
TableTonic ticket booth TICKET № 0001

— options —

Naming style

Number

Prefix

Suffix

Your entity (optional)

How many? 12

psst — click any ticket to copy it

— your tickets —

No tickets yet.
Hit PRINT NAMES to tear some off.
    Honest limits: suggestions, not guarantees. Check reserved words (order, user, table) and your framework's conventions — e.g. Rails expects plural snake_case (line_items) while some teams standardize on singular.
    • Pluralization follows common English rules; review irregular nouns.
    • Uniqueness within a batch is enforced, but not against your real schema.

    How it works

    1 · Pick a flavor

    Choose case style, singular or plural, and optional prefix/suffix stamps. Defaults follow the most common convention: plural snake_case.

    2 · Print tickets

    Each click mints a fresh batch from real domain entities — users, orders, invoices, shipments — with proper English plurals.

    3 · Tear & copy

    Click any ticket to copy it, grab the whole roll at once, or download the batch as a .txt for your migration scripts.

    Table naming cheat sheet

    Plural camp

    users, order_items — a table holds many rows, so the name is plural. Rails, Django and most style guides land here. The full debate →

    Singular camp

    user, order_item — reads naturally in queries: SELECT * FROM user. Popular with SQL-first teams. The full debate →

    Join tables

    Alphabetical pairs: categories_products (plural) or role_user (pivot style). Toggle join-table mode above. See examples →

    Quick answers

    Plural or singular?

    Plural snake_case (users, order_items) is the most common convention and what ORMs like Rails expect. Pick one and never mix.

    Prefix with tbl_?

    Usually noise. The table context is already known in queries, so users beats tbl_users. Useful only on chaotic shared servers.

    What about columns?

    Columns go singular snake_case: first_name, created_at. Foreign keys are singular_table_id, e.g. user_id.

    Reserved words?

    Never name a table order, user, table or group. Check your engine's reserved-word list before committing.

    Read the full FAQ → · Full naming guide →