Pico CSS is no longer maintained; v2.1.1 is the last

Pico CSS, a small CSS framework that styles plain HTML without extra classes, is no longer maintained. Its maintainer, Lucas Larroche, archived the project on October 4, 2026, and named v2.1.1 as the final release. His reason points at AI: such tools now write the lean, accessible CSS that Pico was built to save people from writing. The notice was shared on Hacker News on October 30.

Pico has 16.8k stars on GitHub. Its own site says it ended up "powering thousands of websites."

Why Pico CSS stopped

In the announcement on GitHub, Larroche wrote: "Today, AI can generate lightweight, standalone, accessible HTML with just the CSS it needs." A minimal framework for semantic HTML matters less when that is true, he argued.

He also explained why he did not modernize it. Keeping Pico relevant would take a full rewrite. That means plain modern CSS instead of Sass, a CSS preprocessor, plus newer browser features such as OKLCH colors, cascade layers, the Popover API and anchor positioning, all with fallbacks. It would also need a native compiler that strips out unused CSS.

"That would be a different project," the maintenance page says. "Pico CSS stays as it is."

What still works

Larroche was careful to say that existing sites will not break. "Nothing breaks," he wrote.

Part of Pico	Status
Final release	v2.1.1
npm package	Stays online long term
jsDelivr CDN	Stays online long term
picocss.com docs	Stays online long term
GitHub repositories	Archived, read-only
New issues, PRs, releases	None
Code license	MIT
Docs license	CC BY-SA 4.0

The repository was archived with 93 open issues and 32 open pull requests still listed. Those will now never be merged or answered.

Forks, and the name rule

The MIT license lets anyone fork the code. But the name and logo are not covered by it. "The Pico CSS name and logo are not covered by the MIT license," Larroche wrote, so forks should pick their own name. Pico's site links to a page listing community forks without naming any of them.

One group had already stepped in before the archive. In June 2026, a contributor called tonystar opened an issue with the FastHTML web framework project. It said Pico "is not actively maintained (last update was >1 year ago)" and pointed to a maintained fork at anyblades/pico.

That fork released v2.5.0-alpha on June 26, adding a scoped build so Pico's rules do not leak into the rest of a page. A FastHTML contributor tested it in August and called it "Even better than the original, since everything is scoped." The same group also offers a successor called Blades CSS, and the issue says the Grav CMS project has already moved to it.

What this means for developers

• Pin your version now. If you load Pico from a CDN with a loose version tag, pin it to 2.1.1. Nothing new will ship, so an exact pin costs you nothing.
• Self-host the CSS file if uptime matters. npm and jsDelivr are promised "for the long term," but that is a promise, not a contract. One small file is easy to keep in your own repo.
• Do not wait for security or browser fixes. Any rendering bug in new browser versions is yours to patch from here on. Check your layouts after major browser updates.
• Choose a fork with care. anyblades/pico is active and adds scoped CSS, but it is run by a different team. Read its commit history before you switch a production site, and remember it cannot use the Pico name.
• Weigh the maintainer's argument for your own team. If your developers already lean on AI coding tools, a small hand-checked stylesheet may now be easier than any framework. If they do not, a maintained framework still saves real time.