Quickstart

This guide gets you from the first app launch to a working project with tables and SQL output.

Before you start

Open app.dbmodeler.io.
Decide whether your first project will live only in the browser or in a connected cloud provider.
If you plan to use GitHub, GitLab, Google Drive, OneDrive, or Dropbox later, you can skip those connections for now and add them afterward.

1. Complete the first-run wizard

On first launch, DBModeler walks through a short onboarding flow.

Choose the interface language.
Pick appearance preferences such as theme, dark mode, grid visibility, and UI style.
Review optional introduction and integration steps if they are available.
Choose a storage destination when more than one connected option exists.

If you only have browser storage available, DBModeler can skip the storage-choice step and continue directly.

2. Create your first project

From the project list, create a new project and fill in the setup fields:

Project name
Description
Database engine
Default schema
Table engine, when the selected database supports it
Default ID type or generation strategy

Choose values that match the database you expect to export to. DBModeler uses this configuration to drive type suggestions and SQL generation behavior.

3. Add tables and fields

Once the project opens, start modeling the schema in the diagram editor.

Add a new table.
Add fields for the primary key and the first business columns.
Create a second table if you want to model a relationship immediately.

At this stage, focus on getting the shape of the schema into the diagram. You can refine naming and constraints after the initial pass.

4. Create a relationship

Use the visual editor to connect a source field to a target table.

DBModeler handles the relationship as a foreign-key workflow. If a conflict appears, the app can guide you through reusing an existing field or creating a new one.

5. Preview the generated SQL

Open the SQL preview or export flow.

Review the generated DDL.
Confirm the selected engine is correct.
Copy or download the SQL if you want to inspect it outside the app.

The first version of a project generates full CREATE TABLE statements. Later versions can generate migration-oriented ALTER TABLE output.

6. Save a first version

When the diagram reaches a meaningful checkpoint, create a version.

Add a short description of the change.
Review the snapshot or diff.
Keep the version as a stable point before making larger edits.

Versioning is what turns the diagram from a visual draft into a tracked schema workflow.

What to do next

Continue with these guides depending on your next task: