Webly vs OpenDeck

Open every file your AI writes. Webly is a local-first file reader and editor designed for the AI era — open HTML, Markdown, code, JSON, CSV, and PDF files generated by Claude Artifacts, ChatGPT Canvas, Cursor, v0, Bolt, or any AI tool, then edit them and export to standard formats. Supported formats: • HTML / XHTML — pixel-perfect rendering of Tailwind, custom fonts, dark themes, animations • Markdown — typeset preview with serif typography • Code — syntax highlighting for 25+ languages (Python, JS, TS, Go, Rust, Swift, Java, C/C++, SQL, ...) • JSON / CSV — pretty-printed tree view, sortable tables • PDF — full render + text search + select-and-copy • Plain text / XML / TOML / YAML — line numbers + monospace Native features beyond a browser: • Edit mode — modify text, replace images, change links inline in HTML, Markdown, and source code; save back to local storage • One-tap export — PDF (visual fidelity), PNG (long screenshot for social), Word, Markdown • Outline drawer — jumpable table of contents auto-generated from document headings • Asset panels — extract every image, link, code block, and table; download individually or zip all images • Share Extension — receive files from Messages, Mail, AirDrop, or the Files app with one tap • QuickLook extension — preview directly inside the Files app • Dynamic Island Live Activity — current document shown on the lock screen • iOS 26 Liquid Glass toolbar with full dark mode Completely local: Every file is parsed on-device. No upload, no analytics, no third-party tracking SDKs. No account, no cloud, no server. Webly never needs an internet connection to open your files. Who it's for: Developers, researchers, writers, product managers, and students working with AI-generated documents. Why not Safari: Safari can open .html but not edit it. The Files app preview is limited. .md files barely render in messaging apps. Webly handles all of these in one place — and processes everything locally.

OpenDeck is a viewer for self-contained HTML *documents* ("decks"), analogous to a PDF reader or a web browser opening a local page. Decks are content the user explicitly imports (via Files, AirDrop, or the share sheet) — they are not code downloaded to change the app's own features, and the app ships no in-app store or remote-content fetch. Each deck renders inside a sandboxed, cross-origin iframe served from an isolated origin (a custom deck:// scheme on iOS/macOS). The sandbox withholds top-level navigation, so a deck can never replace or reach the app shell or the native bridge. The app's functionality is fixed; decks cannot alter it. (Ref: Guideline 2.5.2.) To test presenting: on first launch the app preloads a short "Welcome" deck plus three example decks (illustrative HTML presentations) — open any of them from the library and move through the slides by tapping the screen (iPhone/iPad), using the on-screen arrow controls or the thumbnail rail, or pressing the left/right arrow keys. To test import: ready-made .deck files are downloadable from the "Examples" section of the home page at https://open-deck.org (smallest is "What Compounding Actually Does", 0.3 MB — direct link: https://open-deck.org/downloads/compounding.deck). Download one on the device, then open it via the system Share sheet → OpenDeck, or from the Files app — it is added to the library. Note: those three decks are also preloaded, and decks are content-addressed, so re-importing one simply refreshes it rather than duplicating; to watch a brand-new deck appear, first delete it from the library (••• → Delete) and then import the downloaded file. (AirDrop'ing any .deck to the device and choosing OpenDeck works too.) The bundled example decks are first-party sample content; any photographs in them are licensed stock imagery (Pexels License, which permits commercial and in-app use). The app collects no data and makes no network requests; everything is stored on-device.