Claude Styles: Make Claude Write in Your Voice

Claude styles are per-conversation presets that control how Claude writes — tone, length, and formatting — without changing what it knows. Pick a built-in style like Concise, Explanatory, or Formal from the "Use style" menu, or build a custom style from a writing sample so Claude mirrors your voice. Styles work in Claude's web and desktop apps.

We write for this site inside Claude every day, and the single fastest fix for "this reads like generic AI" is the Claude styles menu — not a longer prompt. Below we cover the presets, the exact steps to build a custom style, how styles differ from Projects and profile instructions, and the practical tips that make the feature actually stick. New to the product? Our pillar on Claude AI features maps where styles fit.

What are Claude styles?

A style is an instruction set Claude loads for one conversation that shapes how it answers — sentence length, tone, structure, formality — while leaving its underlying knowledge untouched. Mechanically, a style edits the system prompt behind your chat, which is why the change is immediate and applies to every reply until you switch.

There are two kinds. Preset styles ship with Claude: Normal, Concise, Explanatory, and Formal. Custom styles are ones you create, either by handing Claude a sample of writing to imitate or by describing the voice you want in plain language. The custom side is where the claude style feature earns its keep, because a saved style encodes your voice once and reapplies it on demand instead of you re-explaining "keep it short, no bullet lists" in every chat. If you find yourself pasting the same tone notes repeatedly, that instinct belongs in a style — the same way repeated task instructions belong in prompt engineering patterns rather than one-off messages.

The built-in Claude style presets

Every account starts with four presets you switch between from the "Use style" menu. They cover most day-to-day needs before you ever build anything custom.

The practical rule we use: reach for Concise when you already know the domain and just want the answer, Explanatory when you're learning and want the reasoning shown, and Formal when the output leaves your desk and lands in front of someone else. Normal is the safe default for everything in between. Switching costs nothing, so it's worth trying two presets on the same question to feel the difference before you commit to a workflow.

How to use Claude styles

Applying a preset takes three clicks and no setup:

1. Open or start a chat in the Claude web or desktop app.
2. Click "Use style" near the message box at the bottom of the screen.
3. Pick a style — Normal, Concise, Explanatory, Formal, or any custom style you've saved.

The style you choose stays active for that conversation until you change it. It does not follow you into new chats — start a fresh conversation and Claude reverts to Normal, so you reselect the style you want. That per-chat scope is deliberate: it lets you keep a formal thread and a casual brainstorm open side by side without one bleeding into the other.

How to create a custom Claude style

Presets are generic. A custom style is where you teach Claude your voice, and the whole process runs from the same menu:

1. Open the "Use style" menu, then choose "Create & edit styles."
2. Click "Create custom style."
3. Choose your method. Either paste a writing sample — a few paragraphs of your own prose — and let Claude analyze the sentence length, vocabulary, and rhythm, or pick "Describe style instead" to write plain-language rules ("short sentences, no emoji, first person, skip the summary at the end").
4. Name and save it. Your custom style now appears in the "Use style" menu alongside the presets.

Two field notes from building dozens of these. First, the writing sample matters more than its length — a tight, representative 200-word sample beats a rambling page, because Claude imitates whatever patterns dominate. Second, even a three-line description meaningfully shifts the output, so don't wait until you have the "perfect" sample. Describe the voice, use it, and refine the style later as you notice what Claude still gets wrong. Claude custom styles are editable at any time from the same "Create & edit styles" screen.

Claude styles vs Projects and custom instructions

Claude styles are one of three ways to steer Claude, and mixing them up wastes effort. They operate at different scopes and — critically — they stack on every reply rather than override each other.

As Anthropic's own guide to Claude's personalization features lays out, profile instructions load into every conversation automatically, while a style is a per-chat choice you make from the menu. Projects add a third layer — a persistent workspace with its own uploaded context and instructions, covered in our walkthrough of Claude Projects. Because the three combine, a good setup puts durable identity in profile instructions, per-task tone in a style, and shared reference material in a project. Use a style when you only want to change how a single conversation reads; use profile instructions when you want that change everywhere.

Styles are moving to skills

One change worth flagging: Anthropic has confirmed that styles are migrating to skills. Your custom styles carry over automatically, but they arrive disabled by default, so after migration you enable them under Customize → Skills and invoke a style with a slash command like /{style-name}-style. The Concise, Explanatory, and Formal presets go away once the migration reaches your account.

If you already work with Claude Code, this will feel familiar — skills are the same reusable-instruction format we cover in our guide to Claude Code skills, and the shift means your writing style and your task workflows now live under one system. For most users the day-to-day is unchanged; the menu label moves, and a style you never enabled just needs one toggle to come back.

Practical tips to get your Claude writing style right

Claude styles are only as good as the instructions behind them, and a few habits separate the ones that work from the ones you forget you saved.

• Show, don't just tell. A writing sample teaches rhythm that adjectives can't. Pair it with two or three explicit rules to catch the things samples miss, like banned phrases.
• Keep styles single-purpose. One "LinkedIn posts" style and one "internal memo" style beat a single style trying to do both — narrow instructions apply more reliably.
• Layer with profile instructions. Put facts that never change (your name, your product) in profile instructions and reserve the style for tone, so you're not repeating yourself.
• Re-select after a new chat. Styles don't carry over, so make reselecting from the menu part of your habit.

When a style seems ignored, it's usually one of a handful of causes. This table is our first stop:

According to Anthropic's documentation, styles are available across the Claude apps, and on Claude Opus 4.8 a custom style built from 3 writing samples matched our voice on the first try.

Claude pricing at a glance

For the full breakdown of every plan, see our how much Claude costs guide.