The Rise of Block-Based Editors

If you have used any modern blogging platform, note-taking app, or content management system (CMS) recently, you have likely encountered a block-based editor. Instead of a single monolithic text field, these editors break content into discrete, movable pieces called blocks. You can insert a paragraph, an image, a video, a list, or even a kanban board—each as its own block. WordPress's block editor (Gutenberg), Notion, and many others have popularized this approach, and users appreciate the flexibility and visual clarity it provides.

However, while the concept is widely adopted, the implementation is anything but standardized. The only near-universal convention is the use of the / key to insert a new block. Everything else—how blocks are defined, stored, rendered, and interacted with—remains completely proprietary. Each application builds its own block system from scratch.

The Cost of Proprietary Blocks

This lack of standardization creates significant problems for both developers and end users. As a developer, if you want to offer a calendar block, a fancy kanban board, or an image gallery, you must code it yourself. There is no shared library of reusable blocks that work across different platforms. Your users are therefore limited to the blocks you have time and resources to implement. If they see a beautiful block in WordPress or Notion that your editor lacks, they cannot use it.

Furthermore, blocks cannot easily be moved or shared between applications. A block created in one tool is locked inside that tool's ecosystem. This fragmentation stifles innovation and forces users to compromise on features.

Introducing the Block Protocol

To solve these issues, we are creating a new open standard: the Block Protocol. It is a free, non-proprietary protocol that defines how embedding applications (like editors) and blocks communicate. Any block that follows the protocol can be used in any conforming editor, and any editor can host any conforming block—without custom integration.

The protocol is designed to be lightweight and easy to implement. Developers of editors need to write the embedding code only once. After that, their editor instantly gains access to any block built to the protocol. Similarly, block developers can create a block once and have it work everywhere—from blogging platforms to CMSs to note-taking apps.

Benefits for Developers and Users

The Block Protocol brings several key advantages:

• Interoperability: Users can choose from a rich ecosystem of blocks, regardless of which editor they use.
• Reduced Development Effort: Developers no longer need to build every block themselves; they can leverage community-created blocks.
• Open and Free: The protocol is 100% open and free of licensing fees. Sample code and reference implementations are open source.
• Community Innovation: An open-source community can create a vast library of high-quality blocks, from simple text to complex interactive widgets.

Early drafts of the Block Protocol have been released, and we have begun building simple demonstration blocks and a prototype editor that hosts them. The goal is to foster a collaborative community that grows the library organically.

What Can Be a Block?

Almost anything that makes sense in a document or on the web can be a block. Examples include:

• Basic text elements: paragraphs, headings, lists, blockquotes.
• Multimedia: images, videos, audio players, image galleries.
• Data visualization: charts, diagrams, graphs.
• Interactive widgets: calendars, order forms, kanban boards, polls.
• Structured data: tables, contact cards, event listings—especially valuable when blocks can interact with typed data.

Because the protocol is extensible, the possibilities are limited only by imagination.

Join the Effort

If you work on any kind of editor—be it a blogging tool, note-taking app, CMS, or similar—we invite you to support the Block Protocol. By integrating the protocol, you can immediately offer your users a wide variety of block types without extra development. Block developers can reach a huge audience with a single implementation.

The Block Protocol is still in its early stages. We welcome feedback, contributions, and ideas. Let's work together to make the web better—one block at a time.