
What I tested
September 2026 update: This review describes my experience with Paper when I published it in April. I’ve corrected the pricing and Figma comparison below; I haven’t repeated the hands-on test.
I spend most of my working hours inside AI tools, producing deliverables for clients. Paper caught my attention because it addressed a specific annoyance in that work: I could build a design in code, but getting it into a visual tool where I could review and change it was another job.
Paper gave me a way to move between those two parts of the work. That was useful enough to keep testing.
What Paper does
Paper is a visual design canvas built around HTML and CSS. Its MCP connection lets an agent inspect and change a design: read styles, work with text, create artboards, and write HTML to the canvas.
The distinction is the web-based design model, not simply that software has code underneath it. My original explanation blurred that distinction with Figma.
As checked in September, Paper’s pricing page lists 100 MCP tool calls per week on Free and one million per week on Pro. Pro is $20 per editor per month, or $16 per month with annual billing. One million is a high allowance; it isn’t unlimited. Confirm the current limits before buying.
Where it helped me
When I’m working in Claude Code, design elements can live in JSON files, SVG markup, HTML, and CSS. In the workflow I was using, moving those elements into a visual design tool meant exporting and importing files, then checking what survived the trip.
With Paper, I could push elements from my coding environment into the canvas and inspect them there. I could work on the code, review the result visually, and make another adjustment without starting the transfer over. That was the part I liked most.
The connection also worked in both directions. The agent could inspect what was on the canvas and read styles back, instead of treating the design as a screenshot it had to guess at. I could use the visual review to guide the next change.
If your work already moves between code and visual design, that’s a useful thing to test. If you just need a social graphic from a template, it may be a lot of setup for a problem you don’t have.
What I would check before switching
Paper felt more demanding than Canva in my original test. Understanding HTML structure, CSS properties, and how elements nest helped me get useful results. I wouldn’t send a marketer who has never worked that way straight into it and expect the interface to teach the whole process.
I also found myself learning parts of the MCP workflow through experimentation. That observation belongs to the April test. The documentation has changed since then, so use the current setup guide rather than treating my experience as a description of every screen you’ll see today.
The other question is what your team already depends on. A working component library, familiar review process, and existing integrations all have value. A tool that makes one step easier can still create work elsewhere.
The Figma comparison has changed
My original review overstated Paper’s exclusivity. Figma now documents ways for agents to create and modify native content on its canvas. The claim that Figma lacks agent-driven design editing should not guide a purchase decision.
That doesn’t erase what I liked about Paper. It changes the comparison. Try the same real asset in the tools you’re considering and look at what you can still edit afterward, how well it uses your design system, and how comfortably your teammates can review it. I haven’t run a fresh comparison, so I’m not going to declare a September winner from an April test.
What I’d try first
Start with your design language. The agent needs the colors, typography, spacing, components, and examples that make the work yours. I wrote about collecting those inputs in Strategic foundations. The Creative Director beta previously linked from this review is paused; you don’t need it to follow that article.
Then take one asset you actually need to make. Use Paper’s current setup instructions, connect your coding tool, and bring the asset onto the canvas. Change some text, adjust the layout, and inspect the result at the size someone will use it. That will tell you more than a demo of a perfect rectangle.
I liked Paper for this part of my workflow. Whether it earns a place in yours depends on how much time you spend moving between code and design, and whether it makes that work easier for the people who finish and approve it.
For the rest of the production process, read what actually works in AI creative. Choosing the canvas is one decision in that process.
About Marketer in the Loop
I’m Hanna Huffman. Marketer in the Loop is my weekly letter about doing good marketing work as AI changes how we do it. Expect useful ideas, people worth knowing, and things I’m figuring out in my own work.
Published by MultiplAI Growth Partners.