Storage & Persistence

SnapBoard uses a local‑first storage model designed to keep your boards safe, fast, and fully offline.
This page explains how storage works, how data is saved, and what to expect when upgrading from older versions.

Storage Evolution

SnapBoard has gone through two major storage models:

Alpha Storage — .json (Legacy)

Early versions stored all boards inside a single JSON file.
This approach was simple, but it had several issues:

• Markdown content caused escaping problems
• Large cards produced oversized JSON files
• Attachments stored absolute paths
• No schema or migrations
• No isolation between boards

This format is now considered legacy.

Beta Storage — .db (Current)

SnapBoard now uses a structured database‑backed .db file for each board.

This provides:

• safe handling of markdown
• proper schema definitions
• future‑proof migrations
• improved performance
• cleaner attachment handling
• isolated boards (one file per board)

When you upgrade SnapBoard, your old .json board is automatically converted to .db to secure your data.

Board File Format

Each board is stored as:

my-board-name.db

This file contains:

• columns
• cards
• markdown content
• attachments
• metadata
• timestamps
• layout information

SnapBoard does not use cloud sync, accounts, or external services.
Your boards stay on your machine unless you export them manually.

Exporting Boards (.sb Format)

SnapBoard can export a board as a .sb file.

A .sb file is:

• a structured markdown export
• containing SnapBoard‑specific metadata
• designed for portability and backups
• readable as plain text
• importable back into SnapBoard

Important:

SnapBoard does not accept plain .md files as boards.
Boards require metadata that standard markdown files do not contain.

More details are covered in the
Exporting Workspace section.

Auto‑Saving Behavior

SnapBoard automatically saves your board whenever you:

• edit a card
• move a card
• rename a column
• reorder columns
• add or remove cards
• modify attachments

There is no manual save button — everything is persisted instantly.

This ensures you never lose progress during normal use.

Backup Behavior

SnapBoard currently has no dedicated backup system.
The safest way to protect your data is to:

• export your board as a .sb file
• store the export somewhere safe (cloud, USB, external drive, etc.)

We are actively working on new tools focused on:

• automated backups
• scheduled exports
• multi‑board containers
• safer attachment handling

These features will arrive during the Beta cycle.

Current Limitations

SnapBoard’s storage system is still evolving.
Known limitations include:

• No built‑in backup system
• Attachments use absolute paths (improving in Beta)
• No workspace isolation yet
• .sb export is one‑way (import support improving)
• No multi‑board export container
• No encryption or password protection

These limitations will be addressed as SnapBoard matures.