Skip to content

Complete the Initial Wizard

Use the initial wizard to set the base environment for DBModeler before you open your first project.

The first-run flow is designed to establish the defaults the app needs before the editor opens.

  • interface language
  • appearance preferences such as theme, dark mode, grid visibility, and UI style
  • optional provider connections when those flows are available
  • storage preference when more than one provider is already connected

The wizard runs before normal project work starts, so it is the cleanest place to set defaults without carrying them across an already-open project.

The first screen lets you select the application language.

  • The language list comes from the bundled supported locales.
  • The wizard rotates language previews when reduced motion is not enabled.
  • You can keep the language you choose and continue directly from the same screen.

This choice affects the editor UI, not the SQL or project model.

The appearance step sets editor-level preferences before the first project opens.

  • theme
  • dark mode
  • custom palette, when available
  • grid visibility
  • UI style

These settings control how the editor looks and feels, but they do not change the schema data stored in a project.

Depending on runtime configuration, DBModeler can show an introduction step and provider-related setup.

  • The introduction explains the difference between the browser app and any future backend-oriented experience.
  • Integration steps can prepare Git or cloud flows before the first project is created.

If a provider is not configured in the running build, its setup option will not appear.

If only one storage option is available, DBModeler can continue automatically.

If multiple choices exist, the wizard asks where your work should default:

  • browser storage
  • a connected cloud provider

This is a workflow preference, not a permanent lock. A project can still be moved to cloud storage later with the dedicated project flow.

After the wizard finishes, DBModeler opens the project list and the create-project flow becomes available.

The next setup usually includes:

  • project name and description
  • database engine
  • default schema
  • table engine when the selected database supports it
  • default ID type and generation strategy