Back up a local prompt library by keeping one clear working folder, at least one separate recoverable copy, and a routine that proves you can restore the files. A sync service or Git history can help, but neither replaces checking that recovery works.
Local ownership is useful because the source remains under your control. It also means backup is your responsibility.
Identify the source of truth
Choose one folder as the active prompt vault. Avoid keeping several folders named prompts-old, prompts-new, and prompts-backup beside each other. That makes it unclear which version should be protected.
Write down:
- the vault path
- which app or editor changes the files
- whether the folder already syncs
- whether any files contain sensitive information
- who needs access to the restored copy
This short inventory prevents a backup routine from protecting the wrong folder.
Keep the backup separate
A duplicate inside the same laptop protects you from accidental edits but not from loss of the device or disk. Keep a recoverable copy in a separate location that fits your risk and privacy needs.
Possible options include:
- an encrypted external drive
- a trusted cloud storage folder
- a backup service that includes the vault path
- a private remote Git repository for non-sensitive text files
Choose the option after reviewing its encryption, retention, account recovery, and deletion behavior. Do not upload secrets or private source material just because the files are small.
Decide whether you also need history
A current copy helps after device loss. Version history helps after a bad edit or accidental deletion.
Git can provide readable history for Markdown prompts. Some storage and backup services also retain prior file versions. Whichever method you choose, confirm how long history is kept and how a prior version is restored.
Version history is not a complete backup if every copy depends on the same device, account, or repository.
Back up the whole usable prompt
Protect the files that make the library understandable, not only the prompt body. That may include:
- Markdown prompt files
- images or examples referenced by those files
- a short README explaining the folder structure
- templates used to create new prompts
- a list of any excluded sensitive files
Application caches and search indexes can usually be rebuilt. The human-readable source is the important part.
Test a restore before you need it
Once a month or after a major library change, restore one prompt into a temporary folder. Check that:
- the file opens as readable Markdown
- its title and description are intact
- referenced local assets are present
- the restored prompt can be found and used
- the backup date is recent enough for your needs
A backup that has never been restored is still an assumption.
Keep the routine small
A practical checklist can fit in five lines:
- working vault identified
- separate copy current
- version history understood
- sensitive content excluded or protected
- restore test passed
Promptlight indexes the Markdown vault folder you choose, but it does not provide cloud sync or a hosted backup. If the vault lives in a synced, Git-tracked, or backed-up folder, those capabilities come from the surrounding service and configuration.
For the storage model, see Local-First Prompt Manager and Markdown Prompt Library. For organizing the files before protecting them, use Build a Local-First Prompt Vault.
