A single HTML file showed up on Hacker News late last summer with a proposition that sounded, to many, audacious: an entire presentation tool—editor, viewer, real-time collaboration engine, the works—squeezed into 570 kilobytes. No installer, no account setup, no dependency on servers humming somewhere in the cloud. "The boring deck is dead," the tagline announced. "One file killed it."
The post drew 779 upvotes and set off the kind of sprawling technical debate that only Hacker News can sustain: earnest skepticism mixed with genuine curiosity, rippling out across Reddit, developer Substacks, and Chinese tech forums within two days. Bento, as the project calls itself, sits somewhere between a radical rethink of how presentation software should work and the logical conclusion of a broader movement toward local-first, AI-friendly tools.
Whether it's just clever or genuinely useful remains an open question.
One File to Rule Them All
Open a Bento deck in any modern browser and you're not just viewing slides. You're opening the software itself. The .bento.html file carries its own viewer, its own editor, its own presenter mode—plus all your content, stored as plain JSON right there near the top of the file. There's no separation between tool and artifact. Bento combines the presentation editor, viewer, and data within a single HTML file, allowing it to be used without installing additional software.
How does 570KB hold all that? Compression, mostly. The JavaScript and CSS runtime is deflated into base64 chunks, then decompressed on the fly using the browser's native DecompressionStream API. The data block stays plaintext JSON, though, which preserves what Bento calls the "splice/update contract"—meaning you can crack open the file in any text editor, manipulate the JSON directly, and have those changes stick.
It's a neat trick. The system builds on reveal.js for slide navigation but swaps out heavier dependencies like GSAP and ECharts for homegrown animation and charting engines. What you get is a self-contained runtime with features you'd expect from commercial tools: morph transitions between slides, Ken Burns drift on images, count-up number animations, speaker notes with a second-screen view, even a built-in chart engine with tooltips and zoom.
Privacy as Default, Not Feature
Bento ships with no telemetry, no cloud backend, no third-party scripts. The project site claims it loads nothing from outside domains. Update checks? They query a static manifest and send nothing about users or documents back.
Real-time collaboration runs through what the developer calls a "blind relay"—a WebSocket server built on Cloudflare Durable Objects that stores only ciphertext. End-to-end encryption uses AES-GCM, with keys generated client-side when you create a document. Possession of the file is membership. Open a copy and you're automatically in the live session, if one's active. Offline edits reconcile bidirectionally when you reconnect.
The cryptographic model includes role-based access control: owners can create read-only signed copies, rotate keys to revoke old versions, moderate who's in the session. A public "Guestbook" demo on the Bento site lets anyone edit a shared deck live, a proof of concept that's equal parts impressive and slightly chaotic.
There are trade-offs, naturally. Undo during concurrent editing is snapshot-based, which can revert remote changes to the same property. The relay sees connection timing and a hash of your room key—though the project claims to learn nothing beyond that. During the Hacker News launch, one commenter flagged what they suspected was a Cloudflare analytics beacon; the author investigated, attributed it to challenge traffic under load, and asked for reproducible evidence. The exchange had the familiar rhythm of open-source disputes: earnest, technical, unresolved.
Built for Bots
When Bento says "AI-native," it's not just marketing speak. The JSON data model is designed as an API—meant to be read and rewritten by coding agents or pasted into ChatGPT for transformation. The project includes an agents.md guide and a Claude Code skill called "bento-slides" that can download the latest app and generate decks programmatically.
The workflow is straightforward, almost painfully so: copy the JSON block out of the file, let an AI rewrite it, paste the new JSON back in. The change is undoable. One Substack post called this the "natural endpoint" of building slides with Claude Code, noting early adopters converting PowerPoint files into Bento slides via LLM round-trips.
It's the kind of feature that makes sense if you're a developer who thinks in terms of plain text and version control. Whether it resonates with, say, a marketing VP preparing a board deck is another matter entirely.
What's There (and What Isn't)
Feature parity with PowerPoint clearly isn't the goal. But Bento ships with more than you'd expect from a side project: lines, curves, connectors, freeform drawing, polygon shapes, tables linked to charts, video and audio embedding. Small media clips go inline; large ones link out to keep file size manageable. Motion paths, hover reveals, comments that live in the file itself.
A release around the time of the launch added editable morphId attributes to pair independently created elements for smoother transitions, plus 8K fullscreen fill support. (Whether anyone actually needs to present slides in 8K is a question the README doesn't address.)
The editor is desktop-first. Phones can view and present decks reasonably well, the documentation notes, but mobile editing isn't a priority. The product supports eight UI languages and exports to PDF, though the export relies on browser print-to-PDF flows rather than native rendering—which means results vary.
Accessibility is a gap. During the Hacker News thread, one commenter asked about alt text for images and noted its absence in the UI. The author didn't dispute it. No timeline offered for when that might change.
The Browser Problem
Here's where things get tricky. Seamless in-place saving—clicking save and writing back to the same file—depends on the File System Access API, which as of this writing remains strong in Chromium browsers but inconsistent in Safari and Firefox. Users on those browsers hit a download-on-save fallback, which breaks the frictionless single-file experience that's supposed to be the whole point.
A Chinese tech site analysis flagged this as a practical constraint for cross-org rollouts, recommending teams trial Bento alongside traditional workflows until browser support converges. The author acknowledged on Hacker News being "on the fence" about hosting or PWA options, wanting to preserve the single-file simplicity but recognizing enterprise features might require it eventually.
It's a familiar tension in web development: the ideals of the open web versus the messy reality of browser implementations.
The Longer Game
Slides is just the opening act. The site teases "Docs" and "Sheets" as forthcoming single-file apps following the same model—entire word processor and spreadsheet environments bundled into standalone HTML files. The project name is "Bento/Suite," and the footer notes all software is MIT-licensed, copyright 2026 by "The Bento/Suite authors."
No company entity, no funding announcement, no pricing, no team roster. The GitHub account behind it joined just days before the launch. The download is the product. It's free and open source, for now.
The Hacker News thread filled with the usual comparisons—TiddlyWiki's single-file wiki lineage, Prezi's zooming canvas, other HTML slide frameworks that came and went. The differentiator isn't novelty so much as integration: editor, runtime, data, and collaboration packaged together and made portable, then compressed down to something you could email as an attachment.
Whether that model scales beyond early adopters depends on several things happening at once: browsers converging on file system APIs, accessibility gaps getting closed, and the "file as software" paradigm resonating outside developer circles. That's a lot of ifs.
For now, Bento is a signal—one among many—of how far you can push self-contained web apps when you're willing to rethink the stack from scratch. Whether it's a glimpse of the future or just an elegant curiosity is something only time, and users, will tell.
