Creating Your First Database in Zero

Once you’ve set up your vault, the next step is to create a database inside it. Don’t let the word “database” scare you — in Zero, a database is simply a custom table for storing your own information.

You can think of it like a spreadsheet — but local, private, and with field-level encryption where you need it.

What is a database in Zero?

A database is a collection of entries (rows) with fields you define. Each field has a type (text, password, date, file, etc.) so data stays consistent.

Common examples:

Password manager — username, password, website, notes
Notes or journal — title, date, long text
Document tracker — file attachment, owner, status
Contacts — name, email, phone, company

How to create a database

Open your vault and click New Database.
Give it a clear name (e.g., passwords, work_notes).
(Optional) Add a short description so future-you knows the intent.
Add fields to define what each row will store.
Save — your empty database is ready to use.

Field types you can use

Type	What it’s for
`text`	Short or long free-form text.
`password`	Hidden input; store as encrypted if you mark it so.
`email`, `url`	Standard contact or link fields.
`integer`, `float`	Numbers (counts, amounts, ratings).
`boolean`	Yes/No toggle.
`date`, `datetime`, `time`	Timestamps and schedules.
`choice`	Dropdown of options you define (stored as safe tokens).
`file`	Attach a file. You can store it on disk (default) or inside the DB for small files.

For each field you can also set behavior:

Encrypted — keep the field encrypted at rest.
Hidden — show as masked in lists; reveal on demand.
Nullable — allow the field to be empty.
Default — prefill a sensible starting value.

Notes about files

File fields can be stored on disk (recommended for larger files) or “stored in DB” (good for small files). Encrypted file fields are kept encrypted at rest and decrypted only when you access them.

Naming & rules (important)

Table and column names are normalized to lower_snake_case.
Leading digits are prefixed with _ automatically.
Reserved/system columns are blocked (e.g., id, created, updated, last_used, deleted_at, salt_id).
Duplicate column names (after normalization) aren’t allowed.

Can I change field types later?

For existing columns, critical settings like type, NULL/DEFAULT, and encryption/hidden can’t be changed in place (to keep data safe). If you need a different rule later, add a new column, migrate your data, and remove the old one.

Example: a simple password database

site — text
username — text
password — password (mark as encrypted + optionally hidden)
two_factor — boolean
notes — text (long)

Create these fields, save, and you’re ready to add rows.

Using a template (optional)

Zero includes built-in templates for common setups (passwords, notes, contacts, etc.). Pick a template to scaffold a ready-to-use structure — you can customize it after.

After you create the database

Add, edit, and delete rows.
Search and filter across fields.
Decrypt sensitive fields on demand while you’re unlocked.
(Optional) Import or export CSV/XLSX when you need to migrate data.

Everything stays local to your device and under your control.

Next Up

Adding and Managing Data in Zero

Creating Your First Database in Zero