Paper
A design canvas that renders in real HTML and CSS, so what you draw is the code your agents ship
Designers and design-minded founders who want a canvas that speaks the same language as their coding agents
Non-technical founders who want to type a prompt and get a finished, hosted app with a database
Paper in context: product setup, workflows, and operations
Most design tools draw pictures of software. Paper draws the software. That one difference is the whole pitch, and it’s why the tool has quietly become a favorite inside teams like Ramp, Lovable, Harvey, and Vercel — and why it just raised a $34M Series A (July 2026) from Accel and ICONIQ, with angels including Lovable’s Anton Osika and Vercel’s Guillermo Rauch.
What it actually is
Paper is an infinite-canvas design tool, in the Figma tradition, but it renders everything natively in HTML and CSS instead of a proprietary vector format. When you place a button, a layout, or a full page on the canvas, you’re arranging real web primitives. That means what you export isn’t a “developer handoff” approximation — it’s production-shaped code (HTML, CSS, React) that an engineer or an agent can pick up directly.
The bet underneath this is specific: as coding agents become the default way software gets built, the design format that agents can read and write natively wins. Figma’s format was built for humans drawing; Paper’s is built for humans and agents editing the same artifact.
The agent angle
This is where Paper separates from the pack. Its MCP server ships roughly two dozen bidirectional tools — agents can both read the canvas and write changes back to it. For comparison, Figma’s official MCP integration has historically been read-only with a handful of tools. In practice that means you can point Claude Code or Cursor at a Paper canvas and have the agent iterate on the actual design, then push the result toward production, without the usual copy-paste-translate loop between design and code.
Paper leaned into where designers were already going. When it saw teams moving to Claude Code, it shipped Paper Desktop to sit alongside that workflow — and says it 25x’d ARR in the month after that launch. It’s now a paid product for thousands of teams, and it’s expanding past design into diagramming, decks, and “a visual interface to your agents” for growth and sales teams.
Who it’s for (and who it isn’t)
Be clear-eyed about the category. Paper is a design-to-code tool, not an app builder. It won’t stand up auth, a database, or hosting for you the way Lovable or Replit will. The sweet spot is a designer — or a founder comfortable in a design canvas — who wants their visual work to become clean, agent-ready code instead of a static mockup. If you’ve never opened Figma and just want to describe an app and get a working URL, start elsewhere.
Pricing
There’s a genuinely usable free tier (100 MCP tool calls/week, limited image generation, invite your whole team). Pro is $16/mo billed annually ($20 month-to-month), which unlocks 1M MCP calls/week, video export, and unlimited storage.
Verdict
Paper is the most credible “design tool built for the agent era” we’ve seen, and the endorsement list isn’t an accident — the people building the coding tools are using it to design them. If your workflow already runs through a design canvas and a coding agent, Paper closes the gap between them better than anything else right now. Just don’t mistake it for a no-code app builder; it’s the design half of the pipeline, done unusually well.
Turn Figma designs or live websites into clean React, HTML, or Vue code that stays on-brand
Anthropic's in-chat design and prototyping tool: prompts to polished prototypes, decks, and one-pagers
AI app builder that lets you generate from a prompt, then refine with Figma-style visual controls