ChatGPT Desktop vs Claude Cowork:
Features, Pricing and Use Cases

I use Claude for almost everything I do. Writing, research, content creation. Actually, using Claude was a no brainer for 2026. Compared to ChatGPT it was just miles ahead. And luckily I never set up my systems in ChatGPT before, so I was able to start fresh using all incredible Claude features from day 1.

BUT, in July ChatGPT finally launched its desktop app with similar "work" features as Claude. I ignored it for a whole month.

I used Codex before and built all my projects in a provider agnostic way, meaning I can switch between Claude Code and Codex anytime. (I cover exactly how to set that up in Locked in.)

Last week however I decided to test the rest of the new ChatGPT ecosystem, mostly because there is one big differentiator compared to Claude: Imagen 2, the insane image generation model that is included in ChatGPT.

So I went through the entire ChatGPT desktop app feature by feature, comparing each of it to Claude. Chat, Work, Codex, Voice, Images, Canvas, Projects, Skills, Connectors. Every one of them gets its own real explanation here: what it does, how to actually use it, and where to find it when the sidebar doesn't make that obvious.

I'm not neutral, and I won't pretend to be. Where Claude genuinely wins something, I'll say so plainly. Where it doesn't, I'll say that too.

What This Covers

• Free, Go, Plus, and Pro, what each tier actually unlocks
• Every feature in the app, explained the way you'd actually use it
• Where Projects and Skills live, since neither one is where you'd guess
• Whether ChatGPT can use MCP connections
• The one feature where Claude wins outright, and why
• Where each tool genuinely breaks

This one runs long. Let's dive straight in.

What Is ChatGPT Desktop, Actually?

Similar to Claude Desktop: three tabs, one app. Chat and Work share a single window, toggled in the message box. Codex sits apart, for anything code-related.

Voice and a built-in browser sit on top of all three, so you can talk to any of them or point them at whatever's already open in your other tab. Claude Desktop landed on the exact same shape independently, Chat and Cowork sharing a window, Claude Code standing apart, which is worth knowing before you assume one app is simpler than the other.

Free, Go, Plus, or Pro: What Do You Actually Need?

There's a tier between Free and Plus now, called Go, and most comparison posts still don't mention it. It is my go to in months I do not have to code or create as much. (FYI, I own a Claude Pro subscription that covers my daily tasks; on usage heavy months I upgrade to ChatGPT Plus instead of Claude Max. This setup gives me more than enough usage on only 40 bucks per month.)

The rule: if you only need chat, Free or Go covers you. The moment Work, Codex, or Scheduled Tasks matter, you're paying for Plus.

Chat

Classic everyday mode. Use it for quick questions, brainstorming, first drafts, web search, all in one conversation, but no local file access.

If you've used claude.ai, this is the same shape you already know. The differences show up in the other tabs, not here. The only major difference is that you can let ChatGPT create images straight from the chat, more on this later.

Work

You can hand Work a brief and your files, walk away, and come back to a finished document, deck, spreadsheet, or Site. It runs on the GPT-5.6 model family and can work on its own for a while, only checking in with you when it needs a decision. You can also give it direct access to your files and computer.

Copy-paste prompt:

Turn this outline and these two reference files into a 45-minute
presentation, sections, timing, talking points. Review its plan
before it starts moving files around, the same review step
Claude's Cowork uses.

Codex

The engineer. Codex can read and edit repositories, run tests, debug, work in a terminal, and now it can also handle multi-repo diff reviews and GitHub PR chats directly inside the desktop app. It's the same job Claude Code does, both sitting apart from the main chat window as their own space.

Skip this tab entirely if you don't build software. Nothing else in the app depends on it.

Voice

Your hand hurts? Talk to Chat, Work, or Codex instead of typing. Start a task, check on it, or redirect it out loud, including steering something Work is already running in the background.

Claude's voice mode is a genuine two-way conversation too, on desktop, mobile, and web. What I couldn't confirm is whether it reaches into a running Cowork session the same way ChatGPT's Voice reaches into Work, so treat that specific comparison as open.

Built-in Browser

One browser, built into the desktop app, same tab, same login. It can see what you see, click around a page, download files, and annotate elements you point it at.

Claude splits this job two ways: the Claude in Chrome extension for regular browsing, plus Cowork's own sandboxed computer-use ability for tasks that need to click through a page. Same capability, different packaging.

What Is the One Feature Where ChatGPT Beats Claude Outright?

This is the one that isn't even close. ChatGPT generates original images natively, inside the same chat, no plugin needed.

I tested it myself: I asked for a full set of on-topic images for a social carousel, one visual style, five slides. It delivered with one prompt (you can tell by the look of the carousel that it needs some improvement), no second tool, no separate login needed.

Claude has zero native image generation.

What it has instead are diagrams and interactive mockups built from code. Also it can do some basic svg drawings. This is genuinely useful for charts and prototypes but not for illustrated or photorealistic images. To match what ChatGPT just did, you have to leave Claude entirely, open a separate image tool, a separate login, and hand a manual copy back in. Alternatively you can connect Claude Code to e.g. Nano Banana or Higgsfield to achieve the same result more seamlessly. In both cases you need another subscription and more steps.

If your work leans on custom visuals regularly, this single feature might decide which tool stays open.

ChatGPT Sites vs Claude Artifacts: Which One Actually Wins?

Canvas used to be ChatGPT's side-by-side writing and code workspace: highlight a sentence, ask it to rewrite just that part, adjust reading level with a slider, all without leaving the document. Used to, because it's gone.

There's no side-by-side Canvas panel anymore, it got retired on May 28, 2026 and folded into the chat itself. What you get now instead: inline writing blocks and code blocks that sit directly inside a chat response, editable in place, with a live preview for code (HTML, React, SVG, Mermaid, Vega charts) and console output for Python. It's the same underlying trick: highlight a section, ask for a targeted revision, get the change without losing everything else. The old Canvas UI survives only on legacy models, GPT-4.5 already retired, o3 retiring August 26, so it's functionally gone for anyone on a current model and you don't need to worry about it.

For short edits and single-response drafts, people who used the old panel daily generally say the inline version holds up fine, maybe faster. For long-form, multi-hour editing sessions where you wanted one document staying visually pinned while you iterated, that spatial anchor is gone, and more than one reviewer called it a real loss, not just a redesign.

There's a second ChatGPT feature that's the actual competitor to Claude's Artifacts: Sites, shipped July 9, 2026 alongside ChatGPT Work. It lets you ask for a full interactive website or app, dashboards, trackers, internal tools, and get back a live, hosted URL. Even a custom domain can be included if you own one. Ask for it directly, or type @Sites inside Work or Codex, and ChatGPT builds a private preview first, then you choose who sees it: just you, specific people, your workspace, or the public internet.

OpenAI's own release notes, last touched in mid-August, still list Sites' public publishing and expanded rollout as blocked in the EEA, Switzerland, and the UK. That didn't hold up for me as I was able to test it from inside the EU. Therefore, treat the official line with some skepticism rather than take it at face value, changelogs don't always get revisited once written. What is confirmed either way: Free and Go don't get Sites at all, paid plans only.

Claude Artifacts do the same core job: they generate something, publish it to a real link, so you can hand it to anyone, no separate hosting step. Every one saves as its own persistent object, playable if it's an app, publishable with no account required on the other end. Since April 2026, Cowork's artifacts can even connect to MCP servers and refresh with live data from a spreadsheet or database instead of going stale the moment you close the tab. The difference from Sites: Artifacts work on every plan including Free, and publishing is a click inside any normal conversation rather than a dedicated workflow.

On a paid plan? Try Sites yourself, the regional block may not match what's written. You still don't have access, or are on Free or Go plans? Claude's Artifacts already does the job today.

Where Do Projects and Skills Actually Live in Each App?

Projects group related chats, files, and instructions into one workspace, so you stop re-explaining context every time you open a new conversation. They're available across all tiers now, including Free.

Since the April 2026 redesign, files aren't attached inside a Project's own settings anymore, which is where people lose time. Every file you upload anywhere, including inside a Project, lands in the Library, a tab in the sidebar below Images, and you pull from there into any Project.

Library is still mid-rollout, worth knowing if you don't see it. It launched to Plus, Pro, and Business only in March 2026 with the EEA region excluded entirely. As of this past week, OpenAI's own release notes say it's expanding to Free and Go accounts too, including in the EEA, so if it's missing for you, you likely just haven't been reached by the rollout yet. There's no confirmed workaround in the meantime.

To set a Project up: open the left sidebar, click New project, name it something specific ("Q1 client deck" beats "Work"), then drag a file into any chat inside it once. That file is now in your Library and reusable across every other Project too.

Claude's Projects don't work quite the same way here. Each Project has its own separate Files section, and a file you've already uploaded to one Project has to be uploaded again to use it in another. ChatGPT's Library, where one upload is reusable in any Project, is the more convenient system on this specific point.

Skills & Plugins: The Feature That Isn't Where You'd Look

This one's easy to miss entirely. There's no "Skills" item anywhere in the sidebar. It lives under Plugins → Skills, a tab inside the Plugin Directory, not a menu of its own.

Great news on skills. ChatGPT Skills use the exact SKILL.md format Anthropic created and open-sourced earlier for Claude Code. OpenAI didn't invent a competing standard, it adopted Claude's. A skill written well enough to stay format-agnostic can move between the two products.

Similar to Claude, you can build a skill four ways: write it in chat, use the editor, upload a file, or demonstrate it live with Record & Replay. That last one is the interesting one: open Skills, hit the "+", select "Record a skill," then perform the task once, filing an expense, booking a slot, publishing a report. ChatGPT watches and compiles the steps into an editable SKILL.md file you can run again anytime you need it.

Claude has almost the identical move, "Record a skill" sits in the "+" menu inside Cowork, same idea, same pitch: show it once instead of describing it. (I broke down how skills like this work in Teach Claude once.) Availability is the catch on both sides. ChatGPT's official pricing page lists Skills as available across every consumer tier, but plenty of Plus and Pro accounts don't have it live yet. Check your own Plugins tab rather than trusting either the pricing page or this guide.

Can ChatGPT Use MCP Connectors?

The simple answer is yes. And it's not a workaround, it's the same protocol Claude uses. MCP, the Model Context Protocol, is the open standard Anthropic created back in November 2024 to let any AI assistant connect to any external tool through one common interface. OpenAI adopted it across the Agents SDK, the Responses API, and the ChatGPT desktop app itself back in March 2025.

The rule: in plain terms, MCP is the plumbing that lets ChatGPT plug into your other tools, Gmail, Notion, Slack, without OpenAI hand-building a custom connector for each one. If you've ever connected an app inside Claude, you've already used this same plumbing under a different badge.

In December 2025, Anthropic handed MCP's governance to a vendor-neutral foundation, so the same server that powers a connector in Claude can power the identical connector in ChatGPT. In practice, that means three doors: individual users on paid plans connect remote MCP servers through Developer Mode, Business and Enterprise workspaces can publish vetted MCP apps org-wide, and developers can wire any MCP server straight into the Responses API.

Full read-and-write MCP support, not just read access, is still rolling out in beta and currently favors Business, Enterprise, and Edu plans over individual Plus and Pro accounts. Documented friction is real too: custom apps intermittently vanishing from the directory, OAuth completing without the connector showing up in chat, and developers reporting the same MCP server behaving better inside Claude than inside ChatGPT.

If MCP is central to your workflow today, Claude's connector directory is the calmer starting point. ChatGPT's support is genuine, it's just newer and rougher at the edges.

Scheduled Tasks

Set a task once, have it run once, repeat on a cadence, or watch for changes, all from the sidebar on desktop, web, and mobile. Claude's Cowork has had the same capability since February 2026, comparably mature, so this one's a tie rather than a Claude-only feature.

Both need the app open and the computer awake for a local run; also both are rolling out remote execution that doesn't.

Memory

ChatGPT's memory setting is per-project now. This lets you choose whether a Project draws on your general memory or stays scoped only to what's inside it. Claude's Projects work the same way, context kept to the workspace it belongs to.

Where Does Each Tool Actually Break?

ChatGPT:

• Skills and full MCP support are unevenly rolled out, the pricing page and the real account experience don't always match.
• The surface still asks you to track three tabs and where a given feature actually lives, Plugins hosting Skills being the clearest example.
• Community reports of MCP connectors misbehaving are common enough to plan around, not dismiss.

Claude:

• No native image generation, at all. The one gap in this guide that's not close.
• Windows user-only quirk: Cowork's desktop app needs Windows Pro, Enterprise, or Education, since Windows Home doesn't ship with the Hyper-V it runs on. Mac has no such gate. It also runs from the browser and mobile now regardless of OS, so this only bites Windows Home users who need it touching local files.
• Three tabs still means three mental models, the same complexity tax as ChatGPT under a different logo.

In a Nutshell

Neither app wins the whole job anymore, they've converged too far for that. What's left are specific differences: images, a publishable artifact, an MCP connector that shows up when it should.

Pick the tool for the task:

• need native images? pick ChatGPT
• need a good artifact you can share with your colleagues? Claude is your man
• you like Claude's way of talking to you more? you know what to do

Me for my part will set up my most important projects in both. Luckily copy pasting instructions and uploading skills that are written in a model agnostic way make it possible.