The little details matter.

The self-hosted server stores app records in SQLite and uploaded images as files in its data directory. The desktop app uses its own application-data folder on your computer. Your desktop and web vaults are separate unless the desktop app connects to that web server.

Each vault has one owner account, created on first use. A server asks for a one-time setup code from its log, so only the person running it can create the owner. The owner can require sign-in, and change the username or password, in Data & settings. If sign-in is turned off, only expose the server on a trusted network or behind an authenticated proxy.

Yes. Export in Data & settings saves one .zip with your records, miniature photos, and installed plugins. Restoring it lets you merge into the current vault or replace it. Your account and password are not included.

Yes. At first launch, choose the bundled local server or connect to an existing Paintwarden server. You can switch that choice later in Data & settings.

A desktop vault running on your computer can be used without a separate remote server. A desktop app connected to a remote server needs that server to be reachable. The self-hosted web app needs its server running.

From plugins. Paintwarden doesn't bundle a catalog, so a new vault starts empty. Open Data & settings → Plugins and add a public GitHub repository or upload a plugin .zip to install its paints, color schemes, and miniature templates.

Yes. Create plugin in the Plugins dialog packages your own paints, schemes, and templates as a .zip. Publish it as a public GitHub repository, or send the .zip so others can upload it.

It compares the catalog's screen colors. A high score does not guarantee two paints look identical on a model. Finish, opacity, primer, and lighting can change the result.

No. It saves a new reusable scheme with your reviewed paint choices. The original scheme remains available.

Yes. Use Add paint in the Paints library to create a custom color entry.