Media
1 item
Description
Clip recipe pages into a clean, ad-free reader. 100% local, no tracking. Every recipe blog: a 1200-word introduction, three autoplay videos, a pop-up newsletter, and the actual recipe buried somewhere near the bottom. Just Recipes cuts through all of it. Click the extension icon on any recipe page, hit "Save", and the extension extracts exactly what you came for — name, ingredients, instructions, times — into a clean serif reader. No ads. No "my grandmother first told me about this dish." No SEO preamble. ✦ HOW IT WORKS Recipe pages on most major food sites ship schema.org `Recipe` markup in a machine-readable format called JSON-LD. Just Recipes reads that markup, normalizes it, and saves it locally on your device. The clean reader renders only the useful content in a print-friendly layout. ✦ FEATURES • One-click save from any page with structured recipe data • Flattens nested "chapter → step" instructions into a single numbered list • Parses ISO 8601 times (PT1H30M = 90 minutes) • Clean reader with serif typography, print-friendly CSS • Search saved recipes by name, ingredient, cuisine, category, author, or keyword • Export your full library as JSON • 100% local — no account, no server, no analytics ✦ PRIVACY No data ever leaves your device. The extension makes zero outbound network requests. Saving a recipe is a one-time snapshot from the page you are already viewing. Uninstalling the extension deletes everything. Permissions: storage (save locally), activeTab (read the current tab only when you open the popup), scripting (inject the data-extraction function once per open). No host permissions, no background service worker, no network activity. ✦ WORKS ON Any page that publishes schema.org `Recipe` JSON-LD — the standard structured-data format used across most major food blogs, newspaper cooking sections, and independent recipe sites. If the "Save" button shows up when you open the popup, the extension has found a recipe. Sites that render JSON-LD client-side after page load may not be detected on first try — a planned v1.1 retry will handle those.