Skip to content
SlashSnip
Back to documentation

Operations

Import and Export Snippets (JSON)

Learn how to export your SlashSnip snippets as a JSON backup and import them on another device — the current migration path while cloud sync is pending.

Published March 14, 2026Updated March 14, 2026

Current migration model

SlashSnip does not ship cloud sync yet. The honest current path is manual export/import.

That means:

  • export on device A
  • import on device B
  • verify the trigger flow locally

Why this matters for product messaging

If the product is local-first and cloud sync is not shipped, the docs should say that directly. A vague promise like "your data follows you" creates drift immediately.

Recommended operator checklist

  1. Export before major cleanup or migration.
  2. Keep one known-good backup.
  3. After import, test:
    • //hello
    • one personal shortcut
    • /// menu
    • one variable-based template

When to mention future sync

Only as roadmap language, never as present capability.

Continue the workflow

Compatibility Playbook

Verify the target surface before you standardize a workflow.

Starter Pack Article

Turn the docs into the first practical snippet bundle.

Browse related articles