They are visual or clickable results that Claude builds for you, instead of plain text.

A design is a visual piece of work, such as a poster, a one-page summary, a slide layout, a mockup of an app screen, or a landing page for a product. An interactive page is something you can use, not just look at. It might be a calculator that updates as you type, a quiz that scores your answers, a chart you can filter, or a form that responds when you fill it in.

Both kinds of results are built from standard web building blocks, so they can be opened in a normal browser. Claude writes the structure and styling, shows you a live preview, and lets you ask for changes in plain language. You do not need to know how to code to describe what you want and see it appear.

When Claude makes something substantial, it often appears in its own panel next to the conversation.

In the Claude apps, longer and self-contained results are often shown in a dedicated panel called an artifact, separate from the chat. According to Anthropic’s help center, artifacts are for content that is significant, stands on its own, and is something you are likely to edit, reuse, or build on, rather than a quick reply. Examples include documents, web pages, diagrams, vector graphics, and small interactive tools.

Having the result in its own window makes it easy to look at it properly, ask for changes, switch between versions, and share it. You keep chatting on the left, and the artifact on the right updates as you go. The exact interface and the names of the types may differ by version and plan, so check the current help center if yours looks different.

Anthropic has also introduced a product focused on visual creation.

In 2026, Anthropic introduced Claude Design, an experimental product from Anthropic Labs for creating polished visual work through conversation. It is aimed at things like prototypes, slide decks, one-pagers, and landing pages. The idea is to give designers room to explore many directions, and to give people without a design background a way to produce visual work that looks considered.

Anthropic’s materials describe features such as using a team’s design system so that results match a company’s look, uploading supporting material for context, refining a design through conversation and inline controls, and exporting to formats such as PDF, PowerPoint, or HTML, with a handoff to other tools. Availability, plans, and features for an experimental product can change quickly, so confirm what you can use in the current help center before planning around it.

The first decision is what you are actually making.

Many disappointing results come from a mismatch between the idea and the format. A slide deck, a clickable prototype, and a long document are all different things, and each is judged in a different way. Before you ask, decide what the final thing is, who will use it, and how it will be looked at: on a screen, in a meeting, printed on paper, or clicked through by a customer.

flowchart TD
    A["What are you making?"] --> B{"Will people click
and type in it?"}
    B -- "Yes" --> C["Interactive page or prototype"]
    B -- "No" --> D{"Is it presented
or printed?"}
    D -- "Presented" --> E["Slide design"]
    D -- "Printed or shared as a file" --> F["One-pager, poster, or document"]
    D -- "Just explaining an idea" --> G["Diagram or small graphic"]
        

A short brief with the right ingredients beats a long, vague request.

A design brief is a few sentences that tell Claude what to make and for whom. You do not need design vocabulary. Plain words about purpose, audience, content, and feel work well. The more clearly you describe the goal, the less Claude has to guess, and the closer the first draft will be to what you imagined.

Showing Claude an example is often better than describing one.

Words are a poor way to describe a look. If you have a screenshot of a page you like, a logo, a color palette, or an existing design you want to match, share it. Claude can read images and use them as reference. Designs grounded in real context, such as your brand colors and sample content, usually turn out better than designs made from a few abstract adjectives.

In workspaces built for design, you may also be able to provide a design system, which is a set of rules for colors, fonts, spacing, and components, so that every new design stays consistent with the rest of your materials. When using a screenshot, tell Claude what to take from it, such as the layout, the color mood, or the spacing, rather than asking it to copy everything.

Interactivity turns a picture into a tool.

An interactive page responds to what you do. When you move a slider, the numbers change. When you pick an answer, the quiz marks it. When you choose a filter, the chart updates. This makes interactive pages ideal for explaining ideas, trying out options, and letting other people explore without needing you in the room.

The best results come from several focused rounds, not one giant request.

Once you have a first version, resist the urge to rewrite your whole request. Instead, ask for specific changes one at a time or in a small group. Say what you see and what you want instead. Precise feedback such as “make the headline larger and move the sign-up button higher” works much better than “make it look better.”

Claude keeps earlier versions, so you can switch back if a change makes things worse. It also helps to say what you like. Telling Claude to keep the color scheme while changing the layout prevents it from redoing everything.

flowchart LR
    A["First draft"] --> B["You look closely
and note what to change"]
    B --> C["Ask for specific changes"]
    C --> D["Claude updates the design"]
    D --> E{"Better?"}
    E -- "Yes" --> F["Keep going or finish"]
    E -- "No" --> G["Go back to an earlier version
and try a different change"]
    G --> B
    F --> B
        

You can often change small things yourself and leave bigger changes to Claude.

Some workspaces let you edit directly, for example by changing a heading or adjusting a number in a place you can click. Others work mainly through conversation. A sensible approach is to fix tiny details such as a typo or a name yourself, since that is faster, and to ask Claude for structural changes such as adding a section, changing the layout, or adding a new feature.

Whichever you use, be careful that your manual edits are not lost when you ask Claude for the next big change. If you have edited something yourself, mention it, so Claude builds on your version instead of an older one.

A design that looks good for you may not work for everyone.

Before you share a page, test it in the ways real people will use it. Check that the text is large enough and has strong contrast against its background. Check that buttons are easy to find and large enough to tap. Check how it looks on a phone, because many people will open links on a small screen. Where the page uses color to show meaning, make sure the meaning is also clear without color, for people who see colors differently.

A page can look finished while containing made-up text, so be clear about what is real.

Designs often include sample text, example names, and invented numbers so the layout looks complete. That is fine for a draft, but it becomes a problem if those placeholders slip into something real. A chart with made-up figures, a testimonial from an invented person, or a price that was never decided can mislead people if the page is shared without review.

Tell Claude clearly which parts are placeholders and which are real, and ask it to mark placeholders so that they are easy to spot later. For anything with facts, numbers, or quotes, verify them against your own sources before the page goes in front of others. Do not present invented reviews or endorsements as genuine.

A page becomes far more useful when other people can open it, so think about who gets to.

Claude lets you share what you build, often as a link that opens in a browser. Details differ by product and plan. Anthropic’s help center describes publishing and sharing options for artifacts, and notes that rules can depend on your plan and whether you are on an individual or an organization account. For example, pages made in team or enterprise accounts may be limited to sharing within the organization, and designs in some workspaces use organization-scoped sharing. Product behavior changes, so recheck the current help center before relying on a particular workflow.

A good habit is to treat a new page as private until you have reviewed it. Check who the link is available to, and check what is on the page, before you send it. Remember that a link can be forwarded, and something you shared with one person may reach others.

Sometimes the page needs to live somewhere else.

Not every design stays in Claude. You may need a PDF to print, a presentation file to open in another program, or a web file to place on a site. Anthropic describes export options in its design workspace, such as PDF, PowerPoint, and web files, along with handoffs to other tools, though what is available depends on the product and your plan. For artifacts, you can usually inspect or download the underlying file.

When you need a particular file type, say so at the start. Asking for the format you will need helps Claude build something that exports cleanly. It also helps to test the exported version, because a design that looks perfect on screen can shift slightly when turned into a file for another program.

Knowing the limits prevents wasted effort and unsafe shortcuts.

Interactive pages are powerful, but they are not full software products. They are best for self-contained experiences. Depending on your plan and features, reaching outside services, saving data, or acting on other tools may be limited or may need special features. Third-party guides note, for instance, that a page can respond to clicks and filters but may not be able to trigger other agents or update external tools by itself. Treat such claims as a reminder to check what your own account supports.

A few rules keep your pages trustworthy and safe.

Because a page can look very convincing, it matters what you put on it and how you use it. Do not place passwords, access keys, or other secrets in a page, since pages can be shared or inspected. Avoid collecting sensitive personal information through a simple page unless you have a proper, secure way to handle it. Do not build pages that imitate a real company, an official site, or a login screen to trick people. Claude will decline to create look-alike pages meant to pass as the real thing, and it is wise not to ask.

Be honest about what a page is. If it is a demo, label it as a demo. If numbers are examples, say so. If a layout is a draft, say that too. Honest labeling protects both you and the people who see your work.

Familiar jobs show how the pieces fit together.

Building visually with Claude is fast and powerful, with a few cautions.

These habits cause most disappointing results.

Follow these steps for almost any design or interactive page.

A few popular beliefs about AI-made designs are only partly true.

Quick answers to the questions beginners ask most.

It is a page Claude builds that responds to clicks or typing, such as a calculator, quiz, chart with filters, or clickable prototype, shown in a panel beside the chat.

It is an experimental Anthropic Labs product for creating visual work such as prototypes, slides, and one-pagers through conversation. Availability depends on your plan, so check the help center.

No. Describe what you want in plain language, review the result, and ask for changes in plain language.

The purpose, the audience, the content, the feel you want, and practical limits such as phone or desktop and the number of sections.

Ask for specific changes in small groups, say what to keep, and use earlier versions to compare or go back.

Usually yes, often with a link. Sharing rules depend on your plan and whether you use an individual or organization account, so check the current help center.

Some design workspaces describe exports such as PDF and PowerPoint. Availability varies, so say which format you need and check what your account supports.

Test it with examples where you know the right answer, and compare totals against your original data. A polished look does not prove accuracy.

Be careful. Simple pages are not secure systems. Avoid secrets and sensitive personal data unless you have a proper, secure process and the right permissions.

It should not make look-alike pages meant to pass as the real thing or copy protected designs. Use your own brand, or ask for something original.

Treat the first version as a draft, give specific feedback, and always test and review before you share.

Claude can build designs and interactive pages that you can see, click, and share, from calculators and quizzes to one-pagers, slides, and prototypes. Results often appear in a panel beside the chat, and dedicated design workspaces may offer extra tools for visual work. The best results come from a short brief, real context such as screenshots and brand basics, and several small rounds of specific feedback. Before you share, test the logic, check readability on a phone, label placeholders, review who can open the link, and keep secrets and sensitive data off simple pages. Features and sharing rules vary by plan and change often, so confirm details in the current help center.