Claude's PowerPoint Add-In Has Built-In Web Search — Here's How to Generate a Pitch Deck from Any URL
Paste a website URL into Claude's PowerPoint add-in and it generates a pitch deck matching the site's color scheme. Here's how to use this hidden capability.
Claude’s PowerPoint Add-In Has a Web Search Mode Most People Don’t Know About
Paste a URL into Claude’s official PowerPoint add-in and it will pull the site’s content, extract its color scheme, and generate a pitch deck that matches the brand — all without leaving PowerPoint. That capability is sitting inside the add-in right now, and most people using it for basic slide generation have no idea it’s there.
This isn’t a third-party integration or a workaround. The Claude by Anthropic add-in for PowerPoint ships with built-in web search. You give it a URL, it researches the site, and it produces a deck. In testing, a site with a red-and-white theme produced a presentation that matched that palette on the first pass. Not pixel-perfect, but close enough that the brand connection is immediately legible.
The ~90% first-pass template accuracy claim matters here. When you pre-load your own template before prompting, Claude reads the slide master layouts, fonts, and color scheme and uses them as reference. Combine that with the URL-to-deck workflow and you have something genuinely useful: a client’s website plus your agency’s template equals a first-draft pitch deck in minutes.
Why This Capability Is Easy to Miss
The add-in’s surface-level pitch is “generate slides from prompts.” That’s what the documentation leads with, and that’s what most tutorial walkthroughs demonstrate. The web search capability is mentioned almost in passing — “oh, and it also has web search” — after the PDF upload demo and the basic generation walkthrough.
Other agents ship a demo. Remy ships an app.
Real backend. Real database. Real auth. Real plumbing. Remy has it all.
The mental model most people bring to AI slide tools is: describe what you want, get slides. The idea that you can hand it a live URL and have it do its own research before generating is a different workflow entirely. It’s closer to briefing a junior analyst than prompting a text generator.
That distinction matters for how you use it. You’re not writing a detailed prompt that describes the company. You’re pointing at the company and asking for a deck. The model does the information gathering. If you’ve spent time with Claude’s broader capabilities, you’ll recognize this as the same pattern that makes it useful for research-heavy tasks — the model isn’t just completing text, it’s synthesizing information from a source before producing output.
There’s also a model selection decision embedded here. The add-in offers two options: Opus 4.6 for complex tasks like full deck generation, and Sonnet 4.6 for quick edits and reformatting. For the URL-to-deck workflow, you want Opus 4.6. The web research and content synthesis involved in pulling a site and generating a coherent narrative across four or five slides is exactly the kind of task where the more capable model earns its credit cost.
What the Workflow Actually Looks Like
The mechanics are straightforward. You need a Claude Pro account ($20/month minimum — Max, Team, and Enterprise plans also qualify) and Microsoft PowerPoint on desktop or web. Install happens through PowerPoint’s add-in store: Home → Add-ins → search “Claude” → Add. If that path doesn’t surface it, Anthropic provides a direct install link that works as long as you’re signed into the same account.
Once the sidebar is open, the URL workflow is just a prompt. Something like: “Create a four-page pitch deck based on this website: [URL].” Claude will first research the site, then generate the deck. The transcript from testing shows it pulling brand colors and content structure — the output isn’t a generic template with the company name swapped in, it’s a deck that reflects what the site actually says and looks like.
A few things to set up before you run this:
Load your template first. This is the most important pro tip in the entire add-in. Claude uses whatever is already loaded in the presentation as its visual reference. If you start with a blank file, it invents a style. If you start with your company template, it works within that system. The ~90% first-pass accuracy figure is specifically for the template-loaded workflow.
Set persistent instructions. The settings panel accepts standing instructions that apply to every session: always use this font, always use this color, add speaker notes to each slide. For the URL workflow, you might add something like “always include a slide for company overview, one for key differentiators, and one for next steps.” These instructions persist across prompts within a session, though not across sessions — chat history resets every time you close and reopen PowerPoint.
Use “Ask before edits” mode. The add-in has two edit modes: ask before making changes, or accept all edits automatically. For any workflow where you’re generating a full deck from external source material, ask-before-edits is the right default. You want to review what it’s about to do before it rewrites slides you’ve already adjusted.
The Inputs Beyond URLs
Remy doesn't build the plumbing. It inherits it.
Other agents wire up auth, databases, models, and integrations from scratch every time you ask them to build something.
Remy ships with all of it from MindStudio — so every cycle goes into the app you actually want.
The web search capability is the headline, but the supported input types are worth cataloguing because they expand what the workflow can do.
PDFs work. Upload a sales metrics report, ask for a five-slide deck showing where the company is going — Claude will read the document and generate slides with values pulled from the actual data. In testing with a multi-section sales performance report (monthly revenue summaries, regional breakdowns, rep performance, KPIs), the generated deck cross-checked accurately against the source document.
Excel and workbook files work natively. Claude has strong Excel comprehension, so financial models, forecasting sheets, and data tables can feed directly into slide generation without a PDF conversion step.
Translation works. “Translate this entire deck into French” is a single prompt. The output covers all slides in one pass.
Speaker notes work. “Add speaker notes in English to each slide” generates contextually appropriate notes — not boilerplate, but notes that reflect the actual content of each slide. When the deck was generated from a URL, the speaker notes reflected the site’s content, not generic presentation advice.
The 30MB file size cap is the main practical constraint. Large presentations with embedded images can hit this limit. The workaround is to build in sections and merge afterward.
The Limitation You Need to Understand Before Trusting the Output
Here’s the thing that changes how you verify the output: Claude cannot actually see your slides visually. The add-in processes PowerPoint files to markdown internally. That means graphics, images, and complex visual layouts get converted to text representations — and information can be lost in that conversion.
The practical consequence is chart hallucination. If Claude generates a pie chart, the values it assigns are its best inference, not guaranteed accurate. The good news is that everything generated is native PowerPoint — real editable elements, not images. You can click into any chart and change the values directly. But you have to check them.
This is especially relevant for the URL-to-deck workflow. If the site you’re pointing at has data tables, infographics, or charts, Claude may not capture those values accurately. It will capture the narrative and the brand aesthetic. The numbers need a human review pass.
For AI builders thinking about where this fits in a production workflow: the URL-to-deck capability is strong for first drafts and client presentations where you’re doing the final review anyway. It’s not a set-and-forget pipeline for decks that go out without human eyes on them.
This is a broader pattern in AI-assisted document generation. The model’s internal representation of a document is never identical to the document itself — something always gets lost in the translation to tokens and back. Tools like Remy handle a version of this problem differently: you write a spec in annotated markdown, and the full-stack app is compiled from that spec as the source of truth. The spec is what you maintain; the generated code is derived output. The PowerPoint add-in doesn’t have that architecture — the slides are the source of truth, and Claude’s markdown representation of them is the lossy intermediate.
What This Means If You’re Building Presentation Workflows
Hire a contractor. Not another power tool.
Cursor, Bolt, Lovable, v0 are tools. You still run the project.
With Remy, the project runs itself.
The URL-to-deck capability is most valuable in three scenarios.
Competitive research decks. Point at a competitor’s site, generate a four-slide overview, use it as a briefing document for a strategy meeting. The color scheme matching is a nice touch — it makes the deck immediately identifiable without manual formatting.
Client onboarding. Before a kickoff call, generate a deck from the client’s website to demonstrate you’ve done your homework. Load your agency’s template first so the output reflects your visual system, not theirs.
First-draft pitch decks for new business. The workflow is: client sends website, you run the URL through the add-in with your template loaded, you get a first draft in minutes. The draft needs editing — the chart values need verification, the narrative needs your judgment — but the blank-page problem is solved.
For teams running parallel workstreams — say, generating competitive decks for multiple clients simultaneously — the Claude Code git worktrees approach offers a useful mental model even outside the coding context: isolate each task, run them in parallel, merge the outputs. The same logic applies to presentation workflows where you’re generating multiple decks from different URLs at once.
For teams building more complex document automation pipelines, the add-in’s skills and connectors sidebar is worth knowing about. Skills let you define how Claude formats specific types of content. Connectors pull data from external sources. If you’re building a workflow where slides need to pull live data from a CRM or analytics platform, that’s the integration surface to explore. Platforms like MindStudio take this kind of orchestration further — with 200+ models, 1,000+ integrations, and a visual builder for chaining agents and workflows — which matters when the presentation generation is one step in a larger automated process rather than a standalone task.
The add-in doesn’t work on iPad or Android. Desktop and web only. If your team is mobile-first, that’s a real constraint.
One opinion: the web search capability is undermarketed relative to how useful it is. Anthropic leads with “generate slides from prompts,” which is accurate but undersells the research-then-generate workflow. The difference between “describe a company and get slides” and “point at a company and get slides” is significant for anyone doing client work or competitive analysis. The former requires you to do the research and translate it into a prompt. The latter offloads the research step entirely.
Getting Started This Week
The install takes about two minutes. PowerPoint → Home → Add-ins → search “Claude” → Add. Log in with your Claude Pro credentials. Load your template. Run this prompt:
“Create a four-page pitch deck based on this website: [URL]. Match the site’s color scheme and focus on the company’s core value proposition, key differentiators, and a clear call to action.”
Use Opus 4.6, not Sonnet 4.6, for this workflow. Keep “Ask before edits” on. Review every chart value before the deck leaves your hands.
Coding agents automate the 5%. Remy runs the 95%.
The bottleneck was never typing the code. It was knowing what to build.
If you want to push further, add persistent instructions in the settings panel before you run the URL prompt. Something like: “Always add speaker notes to each slide. Always include a title slide, an overview slide, a differentiators slide, and a next-steps slide.” Those instructions will shape every generation in the session without you having to repeat them.
The Claude design capabilities conversation has been mostly about prototyping and landing pages, but the PowerPoint add-in is a different surface — one that’s already embedded in the tool most business people use for presentations. The web search mode makes it meaningfully more useful than a prompt-to-slides generator. It’s worth an hour of your time to see where it fits in your workflow. And if you find yourself wanting to understand the model’s effort and reasoning tradeoffs as you push the add-in harder, Claude’s effort level settings are worth a read — the same principles that govern how much compute Claude applies to a coding task apply to how thoroughly it researches a URL before generating your deck.
