On Wednesday, August 19, 2026, midway through the closing fireside chat of WordCamp US 2026 in Phoenix, release leads paused the conversation to press the button on WordPress 7.1, which quickly racked up hundreds of thousands of downloads. Matt Mullenweg then turned to something much smaller: a single, self-modifying PHP file he calls a Piplet. The official event recap folded it into a long round-up of everything else that happened on stage, which is exactly why it is worth pulling out on its own. Let’s walk through what he showed and why it matters, together!
What exactly is a Piplet?
According to the official WordCamp US 2026 recap published on WordPress News, a Piplet is a single self-modifying PHP file that stores its own data, with no database and no third-party packages. One file can hold up to 25 megabytes, roughly four million words, and loads in about 50 milliseconds. There is no database to configure, no plugin dependency to install, and no server stack beyond PHP itself. For a site builder used to the MySQL-backed database that WordPress Core normally queries on every page load, that is a genuinely different shape of tool: one file carrying both the code and the content it manages.
Where does the idea come from?
Mullenweg traced Piplets back to 2007. According to event coverage, he could not find the original code and reportedly rewrote the concept from scratch with an Automattic colleague specifically for this fireside chat. A nineteen-year-old idea, reportedly rebuilt from memory rather than from a surviving repository, is what reopened the conversation about simplicity at WordCamp US 2026. He also floated, without committing to it, the idea of a WordPress.org directory where people could publish, fork, and remix their own Piplets.
A fireside chat, not a product launch
The session, titled “Pull Up a Chair for the State of Open Source,” paired Mullenweg with Robert Jacobi for an open conversation about where open source stands today, closing with roughly thirty minutes of audience questions on AI licensing, data centers, and why open source communities compete more than they collaborate. The same conversation also touched on shorter WordPress.org profile links, with w.org/@username redirects like w.org/@matt already live, and on Mullenweg’s wish to reward contributors for their actual impact rather than for pledges made through the Five for the Future program. Piplets came up as one thread among several, not as a standalone headline announcement.
The bigger thesis: why Mullenweg wants WordPress known for simplicity
Mullenweg framed Piplets as one example of a larger direction: “I want WordPress to be known for simplicity, not just complexity.” He connected that goal to steps the project has already taken, moving from MySQL to SQLite to WordPress Playground, and said he wants to clean up the HTML that WordPress generates on the front end. He also pointed to why AI models now favor simple, self-contained HTML files as part of the same argument, tying Piplets to a wider shift in how software gets built and read, not only by people anymore.
Is this actually coming to WordPress?
Not yet, and we want to be clear about that before you get excited. Piplets is an IDEA revived and demonstrated live on stage, not a shipped WordPress feature: there is no release date, no official wordpress.org page dedicated to it, and no public code repository we could locate at the time of writing. The WordPress.org directory Mullenweg mentioned for publishing, forking, and remixing Piplets is a possibility he raised out loud, not a project anyone has confirmed building. Treat this as a thesis about where WordPress could go, not a feature you will find in your dashboard at the next update.
Our take
Beyond the demo itself, what stands out is the timing: Mullenweg chose the same stage where WordPress 7.1 had just shipped to argue that the project’s next chapter should be measured by how little a site needs, not by how much it can do. If you are evaluating tools for your own site, the practical takeaway is the same one behind Piplets itself: fewer moving parts usually means fewer things that can break. We will keep an eye on whether a Piplets directory or public repository actually materializes on WordPress.org, and update this piece if it does. In the meantime, if you want to see how Mullenweg’s push toward leaner, smarter tooling is already showing up inside WordPress itself, our breakdown of the three building blocks that make WordPress agentic is a good next read.
Photo: Wiseboy Wissebo/Pexels.
