Create, edit, and export useful deliverables
Make a document or presentation, refine it, and check the exported file.
Prepare a small set of source notes. Artifact features depend on the template, plan, and organization settings. Required file-creation capabilities must be enabled. This guide describes the current template-based experience, not the legacy code panel.
1. Specify the deliverable
Ask for a self-contained document or deck in a conversation, or choose a template in Artifacts. State audience, purpose, length, and source material. Ask Claude to identify missing facts before drafting rather than inventing them.
Create a one-page project brief from my notes.
Include: goal, audience, scope, milestones, and open questions.
Keep unknown dates and owners marked “to confirm”.2. Review and edit in place
Open the artifact beside the conversation. Request a precise change, such as shortening a section while retaining its facts. Template-based artifacts also support direct editing. Compare important figures and references to your source notes after each meaningful revision.
3. Export and open the result
Use Export and choose a format the selected template supports. Current Docs support formats such as Word, PDF, and Markdown; Slides support PowerPoint and PDF. Open the downloaded file in its target application and check page breaks, fonts, charts, and links. Export success is not a layout check.
4. Keep work findable
Find saved work in the Artifacts tab. Name the final deliverable clearly, keep source notes nearby, and review sharing settings before sharing a link. Publishing or sharing is a separate action from drafting or downloading.
Practice & self-check
Create a one-page brief, make one targeted edit, export it, and inspect the exported file.
When you’re done, take a moment to check:
Read the official sources
CLI instructions checked against official documentation; API examples tested with simulated responses. Product-account walkthroughs were not performed.