Paper vs Figma: What the Community Says (/Last30Days)

Quick Verdict

Paper bills itself as a design canvas built on real HTML and CSS so AI agents can read and write it natively, and it just forced the design world's incumbent into a corner - an independent Braintrust eval had a headless Claude Code agent rebuild 40 simple and 27 design-heavy web pages through each tool's MCP, and Paper agents looped back to the canvas 3.4 times per session versus Figma's 2.4. But this is not a fair fight on scale: Figma just packed Config India 2026 with 30,000 Friends-of-Figma members, shipped Code Layers, Figma Motion, and Dev Mode updates, and still commands the enterprise - while a loud minority is already walking. "If I was Figma right now, I'd be very, very worried. We just cancelled our enterprise plan," wrote @benoit_chabert in a 109-like Threads post crediting Claude Design, not Paper, for the switch. The real story of the last 30 days isn't Paper toppling Figma; it's AI-native code workflows hollowing out the middle of the design-to-dev handoff.

Paper

Paper's whole pitch is that an AI agent can read the canvas because the canvas is HTML. On its own comparison page, Paper frames itself as "a professional design tool built on real HTML and CSS" against Figma's "proprietary design tool," and that web-native bet is exactly what the Braintrust eval stress-tested - agents treated Paper as a feedback loop, re-reading the canvas 3.4 times per session, and the eval noted "the tools produce different HTML dialects," with Figma writing semantic HTML5 while Paper hands back inline-CSS calls.

The strength practitioners point to is the production handoff: the uithings head-to-head concluded Paper "wins for designers and developers" who want code-native output, and the Paper-vs-Figma-MCP eval showing a 1-per-session edge in canvas loops is the kind of measurable agent-friendliness Paper is leaning on. Paper's own pricing page undercuts the "collaboration is Figma's moat" argument too - the Free plan includes unlimited viewer and editor seats, 100 MCP tool calls a week, and limited image generation, with editor seats only becoming paid on the $16-20/month Pro tier, a notably more generous invite-your-whole-team baseline than Figma's capped free history. The roadmap also shows where Paper is headed next: a component system with props and slots "aligned with code concepts" and a Tailwind CSS export demo, both aimed at letting teams "use your code components" instead of maintaining two parallel design systems. The weakness is simply gravity: in the 30-day social window Paper generated almost no first-party community voice - no Reddit threads, no viral TikToks, no keynote - and the only organic cross-mention is an r/DesignSystems post from a dev building "an open source free alternative to paper and figma" that pulled just 10 comments. The Polymarket "Papertrade" and "Paper Rex" markets circulating this month are a different Paper entirely, so the design tool's actual mindshare is thin.

Figma

At Config India 2026, Dylan Field walked out to a 30,000-member community and Figma shipped Code Layers to close the design-to-code gap. The Instagram recap of Code Layers from dope.motions pulled 33,960 views and 5,938 likes, and @figma pitched the feature directly - "Design & code, finally together on the canvas" - including dropping a prototype into a code layer via Figma MCP. Figma's own blog post confirms code layers moved into open beta on October 15, and the Config India help center recap spells out the mechanics: a code layer "holds real, running code" so designs become live, interactive prototypes sitting directly on the canvas, available on Education, Starter, Professional, Organization, and Enterprise plans, with creating and editing inside a code layer free on all paid plans through November 4. The Figma forum recap and official release notes corroborate the same open-beta rollout, underscoring that this isn't a keynote teaser but a shipped, dated feature with a real pricing on-ramp.

At Figma's keynote the same milestone that drew applause was procedural rather than flashy: the engineer who "merged Figma's 1 millionth PR while he was rehearsing" walked the India crowd through how intent gets captured directly on the canvas, and Field noted India is Figma's second largest community by daily active users and its largest Friends of Figma chapter network outside the US.

Figma's strength is the sheer product surface shipping at once: Figma Motion got an After-Effects-style upgrade (616 likes, 4,968 views on punitchawlaofficial's demo, who showed saving animations as reusable styles), and Dev Mode landed in Codex to the tune of 2,351 likes. The plugin ecosystem is a genuine moat - .sypcreative's "plugins that feel like cheating" run names practitioners can actually install: Rombo (animates layers, hands you CSS), Curve Text, and in the follow-up, Color Generator building a full colour scale from one colour. The company is also hiring hard across Figma Weave, with open Software Engineer and Account Executive roles spanning the United Kingdom, Config India, and Early Career tracks under Business Operations and Customer Operations.

The weakness is an enterprise-defection narrative that keeps surfacing, and it now has a named culprit. Anthropic's own Claude Design announcement positions the tool, powered by Claude Opus 4.7, as letting teams build "realistic prototypes" and apply their design system without code, available in research preview for Claude Pro, Max, Team, and Enterprise subscribers. The Claude Design admin guide confirms it's on by default for Team plans and flips on for Enterprise plans on October 15, 2026 unless owners opt in earlier, meaning the exact tool benoit_chabert credited for cancelling a Figma enterprise plan is now defaulting to "on" across Anthropic's own customer base in the same window. Beyond that cancellation, @modestmitkus posted "bye bye Figma" (68 likes), and on r/figmaStock users openly debate whether "FIG is dead due to SaaS apocalypse," with the top comment conceding Figma survives mainly because "all the UX/UI designers are still locked in the FIG ecosystem." @chalaska captured the ambivalence - Claude Code into a Figma design system was "unusable" three months ago and now "executing better than I expected" (104 likes).

Head-to-Head

The Bottom Line

Choose Paper if you are building with AI agents and want the design canvas to be production HTML/CSS from the first keystroke - the Braintrust eval showing agents re-reading Paper's canvas 3.4 times per session versus Figma's 2.4 is the clearest measurable signal that its web-native output is easier for a headless Claude Code agent to iterate on, and a free tier with unlimited editors per Paper's pricing page removes the usual seat-cost objection to trying it with a whole team.

Choose Figma if your team already lives inside a mature design system and needs collaboration, version history, and handoff that scale - as the top r/figmaStock comment put it, Figma persists because designers are "still locked in the FIG ecosystem," and Config India's Code Layers (now in open beta per Figma's blog), Figma Motion, and Dev Mode in Codex show the incumbent is racing to absorb the AI-native workflow rather than cede it.

The emerging stack

The pattern the community is actually converging on isn't Paper-or-Figma - it's Figma-plus-Claude, with code as the final surface. @maybepratikk shared a "@figma + @claudeai" product-design process (138 likes), @dewsign.design connects Claude to Figma to build out color tokens and component states, and @design_nocodeio gave Claude access to a Figma file and watched it generate "30 screens and states" in 30 minutes, with 10 minutes of cleanup. That workflow is now an official Anthropic product rather than a community hack: Claude Design ships with a dedicated Claude Slides tool for presentations and, per the admin guide, is rolling out to Enterprise plans by default this same month, the same product credited with pulling at least one enterprise customer off Figma entirely. Meanwhile designers like @justinmfarrugia are skipping the static file entirely - "I prototype in the real app now, not Figma" - and @TarunBaskarVD summed up the shift: 2024 was "Design in Figma. Prototype. Hand off to devs," and by 2026 "much of the handoff is just gone." Paper's bet is that when the handoff disappears, the canvas that was code all along wins; Figma's bet, via Code Layers and MCP, is that it can become that canvas before anyone leaves.