Paper review

Paper is a web-based design canvas for teams working across design and code. Instead of treating design as a separate file, it uses an HTML/CSS canvas and connects that work to agents, apps, repositories and data sources. Teams can bring live content from files, CMSs, databases or APIs into canvas layers, edit copy there, then ask an agent to send changes back to the codebase. Paper also syncs design tokens, styles and components between the canvas and codebase. IDE or CLI agents can read and write on the canvas, and handle repetitive tasks such as responsive layouts and consistency checks. Its core proposition is a shared surface where visual work, live content and implementation can meet, not just a canvas for drawing mockups. That distinction matters most to teams already coordinating design changes with code and agent workflows.

Paper’s strongest point is the connection between design work and the codebase. The product brief says designs use web standards and can export as code, while tokens, styles and components can sync between canvas and code. For teams that want to keep those pieces aligned, that is a more direct workflow than handing off static mockups and translating them separately.

The canvas also works with more than hand-built design elements. Paper lists connections to files, CMSs, databases and APIs, so teams can use live content in layers and edit copy in context. The copy-editing flow can then send changes back to the codebase through an agent.

• Agents can connect through an IDE or CLI to read and write on the canvas.
• Responsive variants and consistency checks are examples of repetitive work agents can handle.
• The free plan includes unlimited viewers and editors, so teams can collaborate without paying for seats, subject to its usage caps.

That combination makes Paper most relevant when a team wants design, content and code changes to share a workflow—not simply another place to draw screens.

Paper’s free plan has meaningful usage limits despite including unlimited viewers and editors: the pricing page lists 100 MCP tool calls per week, limited image generation and a 25 MB maximum image size. Teams that rely on agents or larger assets could hit those limits before they are ready to pay.

Pro raises the MCP allowance to 1 million tool calls per week, includes 100 times more image generation per week, video export, a 100 MB maximum image size and priority feedback. The trade-off is per-editor pricing: $20 per editor monthly, or $16 per editor per month with yearly billing. That can make the switch more expensive as paid seats grow; the pricing page does not publish an Organizations price, only custom contracts. A free trial is not published either.

The value also depends on using Paper’s agent and code connections. If a team mainly needs a standalone canvas, the sync and agent features may not justify adding another paid tool. The published product details do not specify plan limits for individual integrations or exports beyond the listed features.

Paper has a free plan, Pro at $20 per editor/month, or $16 per editor/month with yearly billing (20% savings), and custom-priced Organizations plans, according to the pricing information checked November 6, 2026. The jump from free to Pro is a per-editor charge; the annual rate saves $4 per editor/month compared with monthly billing. The pricing information does not state a minimum seat count or give an Organizations price.

Free includes unlimited viewers and editors, but usage is capped at 100 MCP tool calls per week, with limited image generation and a 25 MB maximum image size. Pro raises the MCP allowance to 1 million calls per week and image generation to 100 times the free allowance, and adds video export, a 100 MB image limit and priority feedback. Organizations includes Pro features plus SAML/SSO, admin controls, custom contracts and dedicated support.

No add-ons are listed. The free plan’s unlimited editors alongside Pro’s per-editor billing leaves the paid-seat rules unclear in the published pricing details.

Paper is built to connect canvas work with code: designs use HTML and CSS, and the product describes exporting designs as code and syncing tokens, styles and components with a codebase. It also supports connecting IDE or CLI agents and bringing content from files, CMSs, databases or APIs into canvas layers. That may suit teams already working this way, but the published material does not describe a migration process, supported imports, or how much manual cleanup a move requires.

Before switching, confirm how your existing files and design systems transfer. The published details also do not specify export formats, bulk export, or what happens to canvas content and connections when a subscription ends, so portability and lock-in are open questions—not established drawbacks. We have no Reddit posts or comments in the published material to support claims about why users leave Paper. Teams considering a move away should verify data export and agent or repository disconnection with Paper before committing.