Choosing Output Formats
Audience: professionals who use Claude at work, no coding or API knowledge needed. Verified = checked against Anthropic's documentation or help center on 2026-10-16. Design guidance = widely taught practice, not a documented rule.
Three common formats
| Format | Best for | Notes |
|---|---|---|
| Inline in the chat | Quick answers, short drafts, explanations, brainstorming | Fastest; stays in the conversation |
| Artifact | Something you will edit, reuse or share: a document, deck, design, dashboard, small interactive tool, code, diagram | Opens beside the chat; you can edit, come back to it and share it |
| Structured data (table, list, CSV, JSON) | Data you will paste into a spreadsheet or system, comparisons, extractions | Ask for a specific layout and column names |
Artifacts (verified, from the help center)
- An artifact is "anything Claude makes for you that you'd put in front of someone": a design, deck, document, dashboard or small interactive tool.
- Claude creates one when content is significant and self-contained (typically over 15 lines), something you will likely edit, iterate on or reuse, stands on its own, and you will likely refer back to.
- Available on Free, Pro, Max, Team and Enterprise plans; templates (Docs, Slides, Design) are on by default; some templates are in beta or admin-controlled.
- Artifacts require "Cloud code execution and file creation" to be turned on in Settings (or in organisation settings for Team and Enterprise).
- Paid plans can connect apps to an artifact and store data in it. Artifacts made in chat before September 16, 2026 are "legacy": they keep working and can be shared, but new ones cannot be made that way. (Details change; check the current article.)
Choosing (design guidance)
- Will you reuse or edit it? Yes: artifact. No: inline.
- Will it go into another tool? Ask for the format that tool needs (table or CSV for a spreadsheet).
- Who reads it? A document or deck for others: artifact or file; a quick answer for you: inline.
- Does a machine consume it? Ask for strict structure and validate it (D2.2).
Prompting for format
- Name the format, columns, order and units: "Return a table with columns Name, Owner, Due date (YYYY-MM-DD), Status."
- Ask for one format per request to avoid clutter.
- For data, tell Claude how to show missing values (for example "N/A") instead of guessing.
- Check the result against the source; structure does not prove accuracy.
Exam traps
- Long reusable content left inline and lost in chat.
- Vague format requests ("make it a table") with no columns.
- Trusting structured output because it looks tidy.
- Assuming artifacts work with the setting off.
- Sharing an artifact without reviewing what it contains.
References
- What are artifacts? — checked Oct 16, 2026
Check your understanding
A reusable one-page brief you will edit and share. Format?Show answerHide answer
Answer
An artifact.What must be on for artifacts to work?Show answerHide answer
Answer
Cloud code execution and file creation in Capabilities settings.You need data to paste into a spreadsheet. How do you ask?Show answerHide answer
Answer
Specify a table or CSV with named columns and how to show missing values.