Revolutionizing Web Content: The Promise of a Universal Block Protocol

The Rise of Block-Based Editors

If you've written anything on the web recently—a blog post, a note in Notion, or a page in a CMS—you've likely encountered the block editor. The concept is simple: content is built from individual blocks, each representing a distinct element like a paragraph, image, or video. WordPress popularized this with its block editor, where a simple + button opens a menu of block types to insert. Now, almost every modern editing tool—from blogging platforms to note-taking apps—has adopted a similar interface. The block model is intuitive, flexible, and widely embraced.

The Problem with Proprietary Blocks

Despite this near-universal acceptance, a critical issue remains: blocks are not standardized. While most editors now use the forward slash (/) key to insert a block, everything else is bespoke. Each application implements its own block system from scratch. Want a calendar block? A Kanban board? An image gallery? You'll have to code it yourself—every time, for every platform.

This fragmentation hurts end users. If you're using a specific blog engine, you're limited to the blocks its developers chose to build. Those blocks might be basic or incomplete. You might envy a fancy interactive block you saw in WordPress, Medium, or Notion, but your editor doesn't have it. Blocks can't be shared or moved across apps. Users are trapped within the feature set of their chosen tool.

Introducing the Block Protocol

To break this cycle, we're announcing the Block Protocol—an open, free, and non-proprietary standard designed to make blocks interchangeable across the web. The idea is simple: define a common protocol that any embedding application can use to host blocks. Any block that follows the protocol works in any compliant editor.

This is not a product or a platform. It's a specification—a set of rules that apps and blocks agree to follow. By adopting it, developers can write embedding code once and instantly support thousands of block types. Block creators can build a single version of their block and have it function in WordPress, Notion, Medium, and any other compliant system.

What Can Be a Block?

Almost anything that makes sense in a document or on the web. Traditional content elements like paragraphs, lists, tables, and diagrams. Interactive items like order forms, calendars, and videos. Blocks can also handle structured or typed data—imagine a block that pulls in a live dataset or a Kanban board that syncs with your project management tool. The only limit is creativity.

How It Works

The protocol defines how an editor (the host) communicates with a block (the embedded component). The host provides a context—like the current document state—and the block renders its UI and sends back updates. It's like a contract: the host promises certain APIs, and the block promises to use them. We've released a very early draft of the protocol and built a few simple blocks and a lightweight editor to demonstrate the concept.

All sample code is open source, and we encourage contributions. The hope is to foster a community that builds a vast library of reusable blocks—someone makes a great image gallery block, and everyone can use it.

Benefits for Developers and Users

For app developers, the Block Protocol means less work. Instead of recreating every block type your users might want, you implement the protocol once and gain access to an ecosystem of blocks. New blocks appear automatically as the community creates them.

For block developers, you write one block and deploy it everywhere. No more porting a calendar block to five different platforms. Your block works in any host that supports the protocol.

For end users, this is a dream. You choose the editor you love, but you're not locked into its limited block library. You can use any protocol-compliant block from any creator. Content becomes truly portable—export a page from one app and import it into another, and the blocks come with you.

Join the Movement

We've released an early draft of the Block Protocol and invite you to explore it. If you build any kind of editor—blogging tool, note-taking app, CMS, or anything that manipulates content—consider integrating the protocol. Give your users the power to embed a rich variety of blocks without extra work.

The web works best when its pieces are interchangeable. Let's make blocks universal. Check out the Block Protocol website for the specification, sample code, and how to get involved.