Module 4Tools

Canvas Mode: Documents, Not Chat

Sometimes the best document isn't a document, it's a webpage.

What is Canvas/Artifact Mode?

Standard AI chat is back-and-forth messages. But some tasks need a working document— something you iterate on, edit, and refine. That's what canvas/artifact mode is for.

Different models call it different things:

  • ChatGPT: Canvas
  • Claude: Artifacts
  • Gemini: Can create Google Docs/Sheets directly

But they all do the same thing: separate the conversation from the document. You chat on one side, the document lives on the other.

Chat vs. Canvas Mode

You:
"Write a cover letter"
AI:
[Entire cover letter displayed in chat]
You:
"Make paragraph 2 shorter"
AI:
[Entire cover letter again, with paragraph 2 edited]
❌ The document is mixed with the conversation. Hard to track what changed.

When to Use Canvas Mode

  • Writing documents. Essays, reports, cover letters—anything with multiple paragraphs that needs iteration.

  • Coding. Building a script or function that you'll revise and test.

  • Spreadsheets/tables. Tell Gemini to make a Google Sheet. It's version controlled and collaborative.

  • Presentations. Building slides or structured content.

  • Anything you'll iterate on. If you know you'll say "change paragraph 2" or "add a column for X," use canvas.

When NOT to Use It

Canvas mode has a cost: it eats your context window fast. Use regular chat for:

  • Exploratory conversations. If you're just asking questions and learning, chat is fine.

  • One-off requests. "Write a haiku" doesn't need a canvas.

  • Complex multi-topic discussions. Canvas works best when you're focused on one document.

The Context Window Problem

Here's the catch: when you use canvas mode, the entire document is included in every request. Every time you say "make it shorter," the model reads:

  • The system prompt
  • Your conversation history
  • The entire current version of the document
  • Your latest edit instruction

Canvas mode can consume your context quickly. It's true—long documents in canvas mode burn through your context window fast.

Context Consumption: Document Size Matters

Document: 50 lines (~400 tokens)
400 tokens10,000 token budget
✅ This is fine. Plenty of room for conversation.
Pro tip:

If your document is getting long (500+ lines of code, 10+ page essay), consider exporting it and working on it outside the AI. Or start a new canvas with just the section you're editing. Don't keep a massive document in canvas for 50 iterations.

Canvas vs. Chat: Real Examples

Write a 5-page essay
→ Canvas
Multiple paragraphs, lots of iteration ("expand section 2", "add a conclusion"). Canvas keeps it organized.
Build a Python script
→ Canvas
You'll test it, find bugs, ask for changes. Canvas lets you see the code while chatting about fixes.
Create a budget spreadsheet
→ Gemini → Google Sheets
Native Google Sheets support. Version controlled, collaborative, doesn't eat context.
Brainstorm startup ideas
→ Regular Chat
Just a conversation. No document to iterate on. Chat is fine.
Explain quantum physics
→ Regular Chat
Q&A, not document work. Chat is cleaner.
Write a resume
→ Canvas
You'll tweak bullets, reorder sections, adjust formatting. Canvas gives you a live preview.

Gemini's Superpower: Native Google Integration

Gemini can create Google Docs and Google Sheets directly. This is huge for a few reasons:

✓

Version controlled. Google Docs tracks changes automatically. You can see edit history.

✓

Collaborative. Share the doc with others. Everyone can edit.

✓

Doesn't consume context. The doc lives in Google Drive, not in the chat window.

✓

Works outside the AI. Export to PDF, edit manually, whatever. It's a real document.

Example: "Make me a Google Sheet with columns for Name, Email, Phone. Add 5 sample rows." Gemini creates a real spreadsheet, gives you the link, done.

Canvas Best Practices

✂️
Keep documents focused
Don't stuff 10 different sections into one canvas. One document = one purpose.
🔄
Export and restart when documents get huge
If your document is 500+ lines, export it and start a new canvas for the next section.
📊
Use Gemini for spreadsheets
Google Sheets integration is better than canvas for tabular data.
💬
Switch to chat when you're just discussing
If you're asking questions about the document, not editing it, leave canvas and chat.
🌐
Consider webpages over documents
For shareable content, ask for HTML/React. Host it. Way better than a static doc.

The Webpage Philosophy

Your user said: "Oftentimes the best document is not a document, it's a webpage." This is brilliant. Here's why:

  • Webpages are version controlled (if using Git). Track changes, revert, branch.

  • Webpages are collaborative. Multiple people can edit, deploy, review.

  • Webpages are accessible. Send a link. No downloads, no formats, no compatibility issues.

  • Webpages are interactive. Add buttons, forms, charts. Static docs can't do that.

If you're making something you'll share or iterate on, consider asking the AI to generate HTML/React/whatever instead of a Word doc. Host it as a page. It's cleaner.

The Takeaway

Canvas mode is powerful for focused document work. It separates the conversation from the artifact, lets you iterate cleanly, and keeps the working document visible.

But it's expensive (context-wise). Use it when you're seriously editing something. For casual back-and-forth, stick to chat. And remember: sometimes a webpage beats a document.

Claude's note: Artifacts (my version of canvas) separate the conversation context from the document being edited. This is important because when you say "change paragraph 3," I need to know which document you're referring to. Artifacts provide that persistent reference. Without them, you'd have to paste the entire document into the chat every time you wanted an edit, which would pollute the context even worse. Artifacts don't eliminate the context cost—the document is still part of the payload—but they organize it better and make iteration cleaner.