If you've used a modern web editor—WordPress, Notion, Medium, or any of the dozens of note-taking apps out there—you've seen the pattern. You click a plus button, and a menu of blocks appears. Paragraphs, lists, images, tables, embeds. It's intuitive. It works.
But here's the problem: every single one of those apps built their block system from scratch. Want a calendar block? A Kanban board? An image gallery with a specific layout? Someone had to code it up, test it, and maintain it. And if you're using a smaller platform, you're stuck with whatever blocks the developers had time to implement.
That's the gap the Block Protocol aims to fill. It's an open, free protocol that lets any block work in any compatible editor. Build a block once, and it runs everywhere—WordPress, Notion, any CMS that adopts the standard.
The vision: blocks that travel
The idea is simple. Instead of every app reinventing the wheel, the Block Protocol defines a standard way for embedding applications to host blocks. Any block that follows the protocol can be embedded in any application that supports it.
That means developers can focus on building great blocks, not on porting them to every platform. And users get access to a richer, more diverse ecosystem of content types, regardless of which editor they choose.
Beyond text: structured data meets the web
The protocol goes beyond just visual blocks. Blocks can be typed—they can carry structured data that's machine-readable without screen scraping. Imagine an event block that a calendar app can parse automatically. Or a product block that a shopping assistant can understand.
This is the part that could change how we publish data on the web. Instead of downloading a CSV or Excel file to get a dataset, you could just embed a typed block that any tool can read. The protocol makes that possible.
An early draft, with room to grow
The Block Protocol is still in its early stages—version 0.1. The creators are upfront about that: "It's simple and not very good yet." They're releasing it early to get feedback, build a community, and iterate.
But the ambition is clear. If widely adopted, the protocol could make the open web more modular, more reusable, and more connected. Common blocks would get better over time. Esoteric ones—like a flight route visualizer—could be built once and used anywhere.
A call to action
The protocol is 100% open and free. The team is building sample blocks and a simple editor to demonstrate how it works, and they're hoping to foster an open source community around it.
If you work on any kind of editor—a blog platform, a note-taking app, a CMS—consider supporting the Block Protocol. Write the embedding code once, and your users get access to a growing library of block types. If you build custom data types that belong on the web, support the protocol too.
The pieces are in place. The question now is whether the community will rally around it and make blocks truly interoperable across the web.