Bento Page

Bento Page

The defining architectural choice of Bento Page is its single-file model. Every Bento Page deck is one self-contained HTML file that simultaneously serves as the document format, the visual editor, the runtime player, and the collaboration surface. There is no separate .pptx, no companion .json, no cloud workspace. The same file you email to a colleague is the same file they open in their browser, the same file they edit, and the same file they present from.

Inside that single Bento Page file lives a plain JSON document. The JSON describes every slide, every text block, every chart, every image, every embedded video, and every animation timeline. Because the format inside Bento Page is plain JSON, it is diffable in Git, editable in any text editor, parseable in any programming language, and convertible to other formats by simple scripts. The HTML wrapper around the JSON adds the rendering engine, the editor UI, the chart engine, and the collaboration runtime — all packed into roughly 640 KB.

The single-file model of Bento Page has cascading consequences that users feel immediately. A deck can be archived by saving one file. A deck can be shared by emailing one attachment. A deck can be embedded in a blog post by uploading one HTML file. A deck can be reconstructed from a partial backup by recovering one file. There is no database to migrate, no schema to upgrade, no cloud service to deprecate. Bento Page treats the file as the canonical artifact, and that single decision is what makes the product feel so different from the rest of the presentation-software market.

The future apps inside the Bento Page family — bento/spaces for notes, bento/dash for sheets and tables, bento/vault for secure storage — will all adopt the same single-file philosophy. For anyone who has ever lost a slide to a software migration or a vendor sunset, Bento Page is the radical bet that the file, not the platform, is the durable artifact.