Blog

Why local-first, and what it costs you

·4 min read

Visual Ideas saves your designs to your own browser rather than to a server. That is a deliberate choice, and like every deliberate choice it costs something. Here is the honest version of both sides.

What you get

You can use the entire editor without telling anyone who you are. No email address, no password, no verification step, no account to delete later. Your draft newsletters — which often contain unannounced products, customer names, or internal copy — never leave your machine.

There is also nothing to breach. A service that does not hold your data cannot leak it, and there is no database of designs to be subpoenaed, sold in an acquisition, or mined to train something.

What it costs

Browser storage is genuinely fragile, and it is worth being blunt about this. Your designs disappear if you clear your browsing data, use a "clear cookies and site data on exit" setting, work in private or incognito mode, switch browsers, or move to another device. Some browsers also evict site storage on their own when disk space runs low or a site has not been visited in a long time.

None of that is recoverable. There is no server-side copy to restore from, because the whole point is that there is no server-side copy.

This is why the editor shows a persistent warning about browser-only storage, and why the export button matters more here than in a tool that saves to the cloud.

How to work safely with it

  • Export the design JSON whenever you finish something worth keeping. It re-imports with every block and style intact.
  • Keep those JSON files wherever you already keep work — a synced folder, a repository, a shared drive.
  • Export the HTML too, but remember it is a one-way output: it cannot be loaded back into the editor.
  • Do not rely on the browser tab staying open. Auto-save runs every five seconds, but auto-save is not a backup.

Will there be accounts?

Cloud sync is being tested privately with a small number of invited accounts, and it is not open to the public. When it does open, it will be an option rather than a requirement — the browser-only path stays, because not needing an account to use a tool is a feature and not an oversight.