AI UX PlaygroundNewsletterJoin 2K+ AI designers and PMs on Substack. New teardowns, patterns, and prompts as they drop.

Outputs

Output Format Selection

Let people choose how the answer should be delivered such as Markdown, JSON, CSV, or slides before or after generation. Structure becomes a user-controlled contract.

Interactive demo

Headers, lists, and links

# Q2 renewal playbook

Three steps for account managers before Friday.

Overview

How might we design output format selection so people can trust and act on AI output?

When to use

  • Perfect for data processing tools, content generation platforms, and applications where output format selection improves usability and integration.

When to skip

  • Casual Q&A where format chrome is overkill.
  • Formats the model cannot reliably produce.
  • Downstream systems that already coerce format via API only.

Rules

  • Claiming JSON mode while returning prose fences.

  • No validation that the output matches the selected schema.

  • Changing format mid-stream without restarting cleanly.

  • Hiding format options in buried settings.

Evidence

ProductImplementation
ChatGPTCanvas and code/json oriented outputs on request.
ClaudeArtifacts and structured output styles.
API platformsResponse format parameters for JSON mode.
Data analysis toolsExport-as controls for tables and files.

Real-world examples

See all

FAQ

Where should format selection live?

Near the composer or on the answer toolbar. Power users also need it in API/docs.

Select before generate or after?

Before for strict schemas; after for “convert this answer to CSV.” Support both.

How do you verify structured output?

Schema-validate on the client or server and show errors with a fix action.

How does this relate to export conversation?

Format selection shapes a single answer. Export packages the whole thread.