Build a recipe collection you can still find in two years

How LinkVault stores a recipe library (Stand: 2026-09)

LinkVault keeps each recipe URL in local SQLite storage on the phone or desktop. The library stays readable offline. Cloud sync stays optional.

Capture the page, not a screenshot dump

LinkVault saves the page URL from iOS, Android, the web app, or the Chrome and Edge extensions. Optional AI enrichment can add a summary, tags, and a category. You still own the original link.

Tag by cuisine, not by “later”

LinkVault organizes the collection with tags and categories. A tag such as weeknight or baking survives a new device. Semantic search runs across the saved text, so “sourdough” finds the page you stored in 2024.

Sync only when you want the same vault everywhere

Optional cloud sync uses the LinkVault API and Supabase in the EU. A recipe saved on the phone appears on the desktop after sync. JSON export and import copy the library when you leave a device behind.

Keep it findable in 2028

1. Save the canonical recipe URL, not a social-share wrapper.
2. Add two tags: meal type and diet constraint.
3. Leave the item in the local library; do not rely on the browser’s default bookmark bar.

Stand: 2026-09. These steps use current LinkVault capabilities: offline-first local storage, tags and categories, optional EU sync, optional AI tags, and JSON export.