Canvas is the ChatGPT feature that pulls long-form editing out of the chat stream into its own side panel, letting the model rewrite one paragraph, leave inline notes, or run a code block in place.
The fastest answer, as of June 2026: if Canvas simply never opens anymore, it’s probably not broken — OpenAI removed it. In its GPT-5.5 release notes (May 2026), OpenAI announced that Canvas “will no longer be available in GPT-5.5 Instant or GPT-5.5 Thinking,” and that writing and coding now happen inline through writing blocks and code blocks right inside the chat response. Since GPT-5.5 became the default model, most people who “lost Canvas” are simply on a model that no longer has it.
So before you spend an hour cleaning cookies, check which model you’re on. If you genuinely still have a Canvas panel (on a legacy model) and it opens but won’t accept edits or won’t save, that’s the older browser-layer problem, and the lower half of this page fixes it.
Which bucket are you in?
| Symptom | Most likely cause | Go to |
|---|---|---|
| The Canvas button / panel is just gone; the model writes inline instead | You’re on GPT-5.5; Canvas was removed | Section A |
/canvas does nothing, or “use canvas” no longer triggers a panel | Same — GPT-5.5 has no Canvas | Section A |
| Canvas panel opens but is blank / spins forever | Extension or cookie blocking (legacy model) | Section B, Step 1-3 |
| You edit text, but on save it rolls back to the original | Third-party cookies blocked | Section B, Step 3 |
| Nothing renders inside an app’s built-in browser | In-app WebView | Section B, Step 4 |
Section A: Canvas was removed from GPT-5.5
This is the big change and the one most current reports miss. Confirmed in OpenAI’s official ChatGPT release notes (May 2026): with the GPT-5.5 update, Canvas is no longer available in GPT-5.5 Instant or GPT-5.5 Thinking. The same writing and coding work now happens in the chat itself as collapsible writing blocks and code blocks, not in a separate document panel.
What this means in practice:
- Typing
/canvasor “use canvas” on GPT-5.5 will not open the old side panel. It is not a bug, and clearing cookies won’t bring it back. - The model now returns an editable writing block or code block inline. You revise it by replying in chat (“rewrite the second paragraph to be shorter”) rather than clicking inside a separate canvas.
- Paid users can still reach the classic Canvas for a limited time through legacy models until those models are sunset. In the model picker (top-left model name), look for a legacy GPT-4.x option; if it’s there, selecting it restores the Canvas behavior. OpenAI has said this is temporary, so don’t build a permanent workflow on it.
How to confirm this is your situation:
- Click the model name at the top-left of the conversation. If it reads GPT-5.5 Instant, GPT-5.5 Thinking, or GPT-5.5 Pro, you are on a model without Canvas.
- Ask for something that used to trigger Canvas (e.g. “write a 400-word draft”). If the result appears as an inline block you can expand and copy — rather than a right-side panel — you have the new in-chat experience, and nothing is broken.
If you’re on GPT-5.5 and you want the panel back, your only options are a legacy model (while it lasts) or adapting to in-chat blocks. Everything in Section B below applies only when you do still have a Canvas panel and it misbehaves.
Section B: Canvas opens but won’t edit / won’t save (legacy models)
If you’re on a model that still has Canvas and the panel itself is broken, the cause is almost always at the browser layer: any broken link in the iframe + cookie + WebSocket chain shows up as “Canvas is broken.” Test in incognito first (a 5-minute check), then narrow down.
Common causes, in rough order of frequency
1. Ad blocker / privacy extension strips the Canvas iframe
Canvas is a cross-origin child document (with its own WebSocket) injected into the chat page. uBlock Origin, AdGuard, Privacy Badger, Ghostery, and Brave Shields all block “cross-origin iframe + long-lived connection” by default. Symptom: an empty box on the right, an infinite spinner, or a flash of an error that disappears.
How to verify: open an incognito window (which disables extensions by default), log in, and try Canvas on the same conversation. If it works there, it’s an extension.
2. Browser blocks chatgpt.com third-party cookies
Canvas, rendered inside the iframe, needs session cookies scoped to chatgpt.com (note: chat.openai.com now redirects to chatgpt.com). Safari ITP, Brave Shields, and Firefox strict mode can classify these as cross-site trackers and block them. Note that Chrome’s Privacy Sandbox was shut down in October 2025 and third-party cookies are no longer being deprecated — so on stock Chrome this is rarely the cause unless you (or your org) explicitly block third-party cookies. Symptom: editing seems to work, but on save the text rolls back to the original.
How to verify: DevTools (F12) → Application → Cookies → https://chatgpt.com → check for __Secure-next-auth.session-token. Missing means it’s being blocked.
3. Browser too old / unsupported WebView
Canvas uses ResizeObserver, module workers, and recent CSS container queries. Chrome < 117, Safari < 17, Edge < 117, and most in-app WebViews (X/Twitter, Slack, WeChat, Telegram, LinkedIn in-app browsers) won’t run it.
How to verify: visit chrome://version or about:version and check the major version. If you opened the link from an app, copy the URL and paste it into a real browser.
4. Multi-account / SSO workspace mismatch
If a single browser profile is logged into both a personal ChatGPT account and a company workspace, Canvas can send requests to the wrong workspace, the auth check fails, and nothing renders.
How to verify: the top-right avatar shows the active workspace. If it’s not the one you intended, switch workspace, then retry.
Shortest path to fix
Ordered by time-to-test, ascending. The first three steps resolve about 90% of legacy-Canvas cases.
Step 1: Separate extension issues from browser issues with incognito
Open an incognito window in Chrome / Edge / Safari (incognito disables all extensions by default), log into ChatGPT on a legacy model, open any conversation, and ask for a 200+ word draft to trigger Canvas.
- Editing works in incognito → go to Step 2 (extensions)
- Still broken → go to Step 3 (cookies / browser version)
Step 2: Whitelist chatgpt.com in your extension
Don’t disable every extension — just allow the ChatGPT domain:
- uBlock Origin: click the extension icon → with
chatgpt.comopen, click the large power button at the top (grey = disabled for this site) - AdGuard: extension menu → “Disable on this site”
- Brave Shields: lion icon left of the URL bar → “Shields down for chatgpt.com”
- Privacy Badger / Ghostery: “Disable on this site”
Refresh and retry Canvas.
Step 3: Allow chatgpt.com third-party cookies
Chrome / Edge:
Settings → Privacy and security → Third-party cookies
→ Sites allowed to use third-party cookies → Add: [*.]chatgpt.comSafari:
Settings → Advanced → uncheck "Block all cookies"
Settings → Privacy → uncheck "Prevent cross-site tracking" (test only)Firefox:
Settings → Privacy & Security → Enhanced Tracking Protection → "Custom"
→ uncheck Cookies, or add chatgpt.com to the exception listStep 4: Upgrade your browser / escape the in-app WebView
chrome://version shows the major version — anything below 117 needs an update. If you opened the link from an app, long-press the link to copy the URL, then paste it into Safari / Chrome.
Step 5: Clear Canvas’s local storage
If none of the above helps, Canvas’s own IndexedDB / Service Worker may be corrupted:
DevTools → Application → Storage → Clear site data
→ check "Cookies and other site data" + "Cached images and files"
→ Clear site dataThen log back into chatgpt.com. Note: this signs out every active ChatGPT session.
Step 6: Force Canvas with the slash command
On a model that still supports Canvas, type /canvas in the composer (a UI command that opens a blank canvas directly, skipping the model’s intent-detection step), or paste your text with “Let’s refine this section:” before it. If /canvas does nothing, you’re back to Section A — you’re on GPT-5.5.
How to confirm it’s fixed
Open a legacy-model conversation, send /canvas, and confirm the panel opens. Type one line, then refresh the page: if your line is still there after reload, cookies and storage are healthy and saving works.
Prevention
- For Canvas-heavy workflows, keep a dedicated browser profile with only essentials installed (e.g. a password manager).
- Before a long edit session,
Ctrl/Cmd+Athe draft and paste it into a local editor as a backup — a disconnect can lose unsaved edits, and this also future-proofs you against the in-chat-blocks transition. - Don’t run Canvas inside an in-app WebView — iOS and Android in-app browsers almost never work.
- Keep work and personal accounts in separate browser profiles to avoid workspace mismatches.
FAQ
Why did my Canvas disappear after an update? Because OpenAI removed it. As of the GPT-5.5 release notes (May 2026), Canvas is no longer in GPT-5.5 Instant or GPT-5.5 Thinking. Writing and coding now appear as inline writing blocks and code blocks in the chat. Nothing on your end is broken.
Can I still use Canvas at all in June 2026? Temporarily. OpenAI says paid users can keep using Canvas through legacy models until those models are sunset. Pick a legacy GPT-4.x model from the model picker if it’s still listed. Treat this as a short-term bridge, not a permanent setup.
Does /canvas still work?
Only on a model that still supports Canvas (legacy). On GPT-5.5, /canvas and “use canvas” no longer open the side panel — that’s the removal, not a bug.
My Canvas opens but won’t save my edits — is that the removal too?
No. If a panel actually opens (you’re on a legacy model), failed saves are usually blocked third-party cookies. Check for __Secure-next-auth.session-token under chatgpt.com in DevTools, and allow [*.]chatgpt.com cookies (Section B, Step 3).
Is this a Plus / Pro problem or does it hit Free too? The removal hits every tier on GPT-5.5. The difference is that paid users get the temporary legacy-model fallback; Free users move straight to in-chat blocks.
Related
- ChatGPT Deep Research failed
- ChatGPT cookies blocked
- ChatGPT image generation failed
- ChatGPT stuck loading
- ChatGPT network error
Tags: #ChatGPT #Troubleshooting