CodePen 2.0 launched on July 23, 2026. It is the biggest rewrite of the front-end code-sharing tool since it started over a decade ago. Co-founder Chris Coyier called it his largest personal career accomplishment, saying 2.0 took more work than building the original CodePen (chriscoyier.net).

The biggest visible change is that the old separate editing panels for HTML, CSS, and JavaScript are now combined into a single editor (DevOps.com). Coyier said 2.0 was built to do everything the old version could do, plus more. A "Classic" block lets users keep the editor looking and working like the original, and 2.0 works with every existing Pen or Project created in the old version (CodePen Blog).

Under the hood, the changes are extensive. CodePen 2.0 now has a file system for organizing project files, a built-in compiler (a program that translates code into something a browser can run), and the ability to split JavaScript across multiple files within a single project. Users can now manage external code libraries through a package.json file, which lets them pull in free, ready-made code packages from npm — a large public registry of JavaScript tools — and lock each one to a specific version so updates don't break their work (CodePen Docs). A new Blocks system provides building blocks you can mix and match within the editor; MJML, a tool for designing responsive email templates, is already available as a block. A "What's New?" page at codepen.io/2/whats-new lists the full set of changes (chriscoyier.net).

Collaboration is now built in. An invite feature lets multiple people edit the same project at the same time, and the platform also supports asynchronous collaboration for teams working across different time zones (CodePen Docs; codepen.io/2/whats-new). A Live View feature lets people interact with a demo while it is still being edited, bridging the gap between writing code and showing it to an audience (CodePen Docs).

CodePen 2.0 can also deploy small websites directly from the editor. That means what was mostly a place to write and share code can now publish live websites on its own (CodePen Docs). Forking, which lets you copy someone else's project and make your own version, is still supported (CodePen Docs).

Getting to 2.0 took years. By January 2024, CodePen 1.0 had been running for 11 years, and Coyier was already calling 2.0 the hardest project he had ever worked on (chriscoyier.net). A March 2026 podcast episode titled "Why 2.0?" explained the reasoning behind the rewrite (CodePen Blog). Coyier streamed himself using the 2.0 editor in May 2025, giving an early public look at the work in progress (chriscoyier.net). Even the documentation site required real engineering work: it was built as a custom setup in WordPress (chriscoyier.net).

Launch day drew community interest. The Keyframers, David and Shaw, reunited and live-streamed using CodePen 2.0 on July 23. ShopTalk Show episode #725 covered the launch on July 27 (ShopTalk Show).

The broader context here is a shift in what browser-based coding tools are expected to do. When CodePen launched in 2012, it was part of a category of "code playgrounds" focused on sharing snippets and quick prototyping. The 2.0 feature set, with multi-file projects, external code libraries, a compiler, collaboration, and deployment, moves CodePen closer to a full development environment that runs in your browser. Tools like StackBlitz, CodeSandbox, and Replit have been moving in the same direction, and CodePen 2.0 narrows the gap between these products.

What sets CodePen's approach apart is that the original editor's simplicity is preserved as a first-class option. The Classic block and backward compatibility with every existing Pen mean the upgrade does not force a workflow change on users who want the old experience. That is a practical design choice: the large collection of existing Pens and the habits of long-time users are treated as assets, not as outdated baggage.

In my view, the deployment feature is the most consequential addition. CodePen has always been a place where front-end work lived publicly, but the output was a Pen, not a website. Letting users publish directly from the editor closes a loop that previously required exporting code and finding hosting elsewhere. For small projects, demos, and portfolio sites, that removes a real friction point. Whether it pulls users away from dedicated hosting services or simply adds convenience for existing CodePen users is a question the next few months will answer.