Canvas: the writing partner you didn't know you had.
Canvas is ChatGPT's side-panel editing surface — a persistent workspace for text or code where you iterate, refine, and ship. Most people ignore it or trigger it for trivial things. Here's when it genuinely changes the work, when it gets in the way, and the patterns that make it a real writing partner.
Canvas is for work, not chat.
Regular chat is a scroll: every revision re-pastes the whole thing and pushes the last version off-screen. Canvas pins the document in a side panel so you can point at a specific paragraph, edit it in place, and keep a version history. It's the difference between chatting about a thing and building the thing.
The catch is knowing when it earns its place. Force it on a one-line answer and it's just friction.
Edit one paragraph at a time.
This is the move that makes Canvas worth it: highlight a specific section, ask for a targeted change, and only that part updates. Click each paragraph below to select it, then apply the edit. Watch the version count climb.
Force it, and use the version history.
ChatGPT opens Canvas automatically for some outputs and misses others. When it doesn't, just ask:
And Canvas tracks versions. You can roll back to an earlier draft, branch a new direction from there, and keep the winner — which is what makes a long session productive instead of a one-way street you can't undo.
Make the call.
Four situations. Pick the right move for each.
Build the next thing in Canvas.
Write something real in Canvas
Pick a real piece of writing you owe someone — a blog post, a memo, a long email. Do the whole thing in Canvas: force it open, use point-and-refine on specific paragraphs, lean on version history when a direction doesn't work, and ship it from there. Notice how different it feels from scrolling chat.
What you can do now
- Invoke Canvas for substantial writing or code — and skip it for quick chat
- Use highlight-and-edit for surgical, one-section-at-a-time refinements
- Use version history to branch and recover from a bad direction
- Step back for a holistic pass after a run of micro-edits
- Copy important drafts out as you go, since versions don't always persist