Claude for Excel — What Works in 2026, What Still Doesn’t
Anthropic shipped a real Claude for Excel sidebar add-in on January 24, 2026 — it edits pivots, charts, and conditional formatting natively in the workbook with cell-level citations. If you do most of your spreadsheet work inside one .xlsx on Microsoft 365, it’s genuinely the best tool in its category. The structural limits sit elsewhere: it can’t see your Google Sheet sitting one tab over, can’t query your Postgres in the same conversation, can’t schedule a Monday-morning Slack report, and can’t open a pull request when the analysis points at code in your repo. This page is the honest assessment of what Claude does well for Excel today, where it stops, and what to use instead when those limits become the workflow.
Where Claude actually wins for Excel
The add-in landed in January 2026 and closed many 2024-era gaps. These are the four workflows where Claude is genuinely the best tool in its category today.
Editing pivots and charts inside Excel
The Claude for Excel sidebar add-in (GA on Pro since Jan 24, 2026, install via Microsoft AppSource) edits pivots, conditional formatting, and chart axes with cell-level citations. For the day-to-day Excel-author workflow — refresh a pivot, swap a chart series, fix a formula — the add-in is genuinely best-in-class because it lives inside the workbook and writes back natively.
Reasoning over a clean dataset that fits one sheet
Once your data is loaded, Claude is the strongest reasoner in the category. Open-ended questions like "why might Q3 revenue be flat despite trial signups doubling?" — pattern-spotting, hypothesis generation, pushing back on shaky conclusions — are where Claude beats every other model. If your week is dominated by interpretive questions on one workbook, the add-in plus claude.ai is the right home.
Cross-app context across Word + Excel + PowerPoint
Anthropic shipped Skills + shared context across the Office suite in March 2026. A Claude session that reads your Excel can also draft the corresponding PowerPoint slide and Word memo without re-uploading the data. For document-heavy finance / consulting workflows — where the deliverable IS a deck or memo — this is unique.
Charts inline via Code Interpreter
claude.ai consumer ships a Code Interpreter sandbox that runs Python in a micro-VM and renders charts inline — no copy-paste-to-notebook step. For one-off visualizations on a clean upload it's quick. The tradeoff: charts live in the chat session, not in a savable shareable dashboard with a refresh schedule.
Where Claude for Excel falls short
Six structural limits that turn into daily friction once Excel work crosses the single-workbook, in-chat boundary.
- 01
Locked to one Excel workbook, locked to Microsoft 365
The add-in only sees the .xlsx that's open in the Excel desktop app on Microsoft 365. It can't query the Google Sheet sitting in the next browser tab, can't reach your Postgres production data, can't pull from Stripe. Most weekly reports stitch 3–5 sources by hand; the add-in solves zero of those joins.
- 02
Per-chat or per-session state
claude.ai uploads expire when the chat ends. Claude Projects pins files via retrieval (max 30 MB per file) — but it pulls relevant slices, not the whole sheet, and the latest version still has to be re-uploaded by hand. The add-in scopes to whichever workbook you have open. Either way, no AI sees your data refresh on its own.
- 03
Drive connector reads Sheets read-only
Anthropic's Google Drive connector reads Google Sheets but exports as CSV behind the scenes — you can't write back, can't refresh on a schedule, can't get a live feed. For the most common business pattern (a Sheet that updates daily and you want Monday-morning analysis on the latest version), the connector is one human export away from useful.
- 04
Charts live in the chat, not on a dashboard
Code Interpreter charts and add-in chart edits are both bound to the conversation or workbook. There's no shared dashboard URL a non-technical teammate opens next Tuesday. There's no "deliver this to #revenue Slack channel every Monday at 6am." The schedule + share layer is missing.
- 05
No native scheduling, no native alerts
Claude has no scheduler. Anything recurring requires a separate cron job + script + delivery pipeline that Claude itself can't host. "Slack me when this metric breaks threshold" is not a primitive Claude exposes.
- 06
No path from analysis to merged code
Claude Code (separate CLI product) can edit code and open PRs. Claude for Excel cannot. If the analysis points at a content fix, config change, or seed-data update in your repo, you copy a snippet into Cursor or Claude Code, switch tools, and ship from there.
4 real Excel tasks where Claude breaks (and what to use instead)
Task 1: Find anomalies in a 50,000-row sales CSV
Claude
claude.ai accepts ~50K rows on Pro within the 30 MB upload cap. Code Interpreter runs a script over them in the chat session. Findings live in the chat — re-running next month means re-upload + re-prompt.
OnlySearch
Drag once, the file persists. Anomaly detection (isolation-forest + IQR + domain rules) runs server-side over the full file every time you ask. Save as a dashboard, schedule weekly.
Task 2: Generate a weekly revenue dashboard from a live Google Sheet
Claude
Drive connector reads the Sheet read-only. You get a one-shot answer in the chat. Each Monday you re-prompt to see the new week's data; there's no scheduled refresh, no Slack delivery.
OnlySearch
OAuth into Sheets once. Ask once for "weekly revenue by category, top 10 SKUs, Mondays at 6am to #revenue." Schedule from the UI. Slack delivery built in.
Task 3: Compare Excel data to Postgres production data
Claude
Excel uploads to claude.ai; Postgres requires a DIY MCP server you build and run yourself. Two contexts, two sessions, manual stitching.
OnlySearch
Both sources native. Single SQL with a CTE pulling one side from the uploaded CSV and the other from Postgres in one round trip. Joined result, chart, dashboard.
Task 4: Excel pointed at a stale config — ship the fix
Claude
Claude for Excel can't edit code in your repo. Claude Code (separate CLI product) can. You copy the analysis context, switch tools, drive Claude Code to the fix.
OnlySearch
Same agent. Edits the repo, runs the test suite, opens a PR — all inside the conversation that surfaced the problem. Data → code → ship.
When to stay with Claude
We’re not the right tool for everyone. Here’s when Claude is the better choice — and we’d recommend it.
- Most of your spreadsheet work is in-Excel authoring on Microsoft 365 — pivot edits, formula composition, chart formatting. The Excel-native sidebar add-in is genuinely the best tool for that surface.
- Your deliverables are Word memos and PowerPoint decks driven by Excel data, all on Microsoft 365. Anthropic's shared-context Skills across Word/Excel/PowerPoint is a real workflow win there.
- You don't have engineering or growth functions on your team and the analysis itself is the deliverable — no code needs to ship from it, no Slack alert at 6am Monday, no cross-source join.
- You're already paying for Claude Pro / Max for general reasoning, writing, and code. Adding a separate data tool is friction unless cross-source / scheduled / GitHub workflows show up regularly.
Common questions about Claude for Excel
Does Claude have an Excel add-in?
Yes — Claude for Excel went GA on Pro on January 24, 2026. It's a sidebar in Excel desktop on Microsoft 365 (Ctrl+Alt+C / Ctrl+Option+C), installed via Microsoft AppSource. It edits pivots, conditional formatting, and chart axes with cell-level citations, and shares context with Claude for Word and PowerPoint. The trade-offs: locked to .xlsx open in M365 desktop, can't see your Google Sheet or Postgres in the same conversation, no scheduled runs, no Slack/email alerts.
What are Claude's limits for Excel?
On claude.ai Pro: 30 MB per file upload, 20 files per chat, ~50K rows of typical business data handles comfortably. Wider schemas (40+ columns or heavy free-text) land closer to 10K rows. Multi-million-row datasets exceed the model's working memory regardless of plan. The Excel sidebar add-in scopes to whatever workbook is open in M365 desktop. Claude Projects pins files (still 30 MB cap per file) but uses retrieval — Claude pulls relevant slices, not the whole sheet.
Can Claude write Excel formulas from natural language?
Yes — and well. "Give me a formula that returns the running total of column B grouped by column A" produces clean Excel formulas with explanations. The Excel sidebar add-in writes formulas inline with cell-level citations, which is smoother than copy-pasting from chat. This is one of the things Claude does best for spreadsheets.
Does Claude work with CSV files?
Yes — both .xlsx and .csv upload to claude.ai (30 MB cap, 20 files per chat). The Excel sidebar add-in is .xlsx-only. For ongoing CSV work — re-reading a file that updates each week, joining a CSV to a database, scheduled CSV → report — the chat-and-add-in surface needs a human in the loop on each refresh.
Why do some users see $100–$200/month bills with Claude on data work?
That's Max-tier pricing ($100/mo Max 5x or $200/mo Max 20x), not metered overage on Pro. Pro is a flat $20/mo. The upgrade pressure: heavy spreadsheet work re-tokenizes the same multi-MB file across follow-ups, which hits Pro's 5-hour rolling window cap quickly and pushes users to Max. The token economics aren't punitive — every reload of the same file is just a fresh tokenization.
How is OnlySearch different from Claude for Excel?
Claude is a brilliant reasoner and the add-in is the best in-Excel surface in the category. OnlySearch fills the gaps the chat-and-add-in shape leaves: persistent file connections (no re-uploading), multi-GB server-side processing, native Google Sheets / Postgres / MySQL / Stripe / GA4 connectors with cross-source single-query joins, scheduled runs with Slack/email alerts, and a coding agent that opens GitHub PRs when the analysis points at code. You can also use Claude as the underlying model inside OnlySearch via bring-your-own-key — same Anthropic plan you're already paying for.
Can I keep Claude and add OnlySearch on top?
Yes — many users do. Keep Claude for reasoning, code reviews, the Excel sidebar add-in for pivot work, and Word/PowerPoint context-sharing. Add OnlySearch for the cross-source + scheduled + ship-as-code workflows where the add-in is structurally constrained. Plug your Anthropic API key into OnlySearch and you're paying Anthropic at metered rates with the persistence/connector/scheduling/PR layer on top.
Connect once. Re-read every Monday. Try OnlySearch free.
Native Google Sheets / Postgres / Stripe. Multi-GB files server-side. Schedule the report, ship the fix as a PR. The free plan refills weekly — no credit card. Use Claude as the underlying model via BYOK if you want.