What VSTO Add-ins Are — and Why the Question Comes Up
VSTO (Visual Studio Tools for Office) add-ins are COM-based plugins written in C# or VB.NET that run inside Windows desktop Office. For years they were the default way to extend Excel, Word, and Outlook with serious logic, and many businesses still depend on them. The catch in 2026 is reach: VSTO add-ins run only on Windows desktop Office. They cannot run on Mac, Office on the web, or mobile, they install per machine, and Microsoft's investment has clearly shifted toward the web-based Office.js model. That does not make VSTO obsolete — but it does make 'should this be VSTO or Office.js?' a question worth answering deliberately.
Key Takeaways
COM-based .NET
Written in C#/VB.NET, with deep access to the desktop Office object model.
Windows desktop only
No Mac, no Office on the web, no mobile — a hard limit for hybrid and BYOD teams.
Per-machine deployment
Installed via ClickOnce or MSI on each device, which complicates rollout and updates.
Deep desktop power
Can reach Win32-level capabilities and advanced automation that Office.js does not expose.
Microsoft favors Office.js
New platform investment is going to web add-ins, so VSTO is effectively in maintenance mode.
VSTO vs Office.js: A Practical Comparison
VSTO still wins in a narrow set of cases: a Windows-only desktop user base, an existing VSTO codebase that works and rarely changes, offline desktop scenarios, or automation that genuinely needs Win32-level depth the web API cannot reach. For almost everything new, Office.js is the better default — one codebase across Windows, Mac, and web, central deployment without touching machines, and a future Microsoft is actively building on.
The deployment difference alone is significant: pushing a VSTO update means redistributing installers, while an Office.js update is just a new web deploy your users pick up automatically. If you are starting fresh, or any of your users are on Mac or the web, that tilts the decision strongly toward Office.js.
Let platform reach decide first
Before comparing features, ask one question: does every user sit on Windows desktop Office, today and for the foreseeable future? If the answer is anything but a firm yes, build Office.js. Reach is the constraint VSTO can never fix, and it is the one that hurts most later.
Keep VSTO where it already works and the requirements are stable. For anything new — or anywhere users are on Mac or the web — choose Office.js, and plan a migration for the legacy add-ins that still matter.
Whether you need advice on keeping a VSTO add-in, migrating it to Office.js, or building something new, our team advises on and executes both. See our page.Office Add-in development services
VSTO add-ins vs Office.js web add-ins (2026)
| Factor | VSTO add-in | Office.js add-in |
|---|---|---|
| Language | C# / VB.NET | TypeScript / JavaScript |
| Runs on Mac and web | No | Yes |
| Runs in new Outlook for Windows | No | Yes |
| Installation | MSI / ClickOnce per machine | No install needed |
| Updates | Redistribute installer | Update the web app |
| Win32/deep desktop access | Yes | Limited by design |
| Microsoft's direction | Maintenance mode | Actively invested |
Frequently asked questions
Are VSTO add-ins still supported in 2026?
Yes, VSTO add-ins still run in classic desktop Office on Windows. However, they do not run in the new Outlook for Windows, Office on Mac, or Office on the web. Microsoft's active investment is in the Office.js web add-in model.
When does a VSTO add-in still make sense?
When every user is on Windows desktop Office with no plans for Mac or web, the add-in needs deep Win32-level capabilities that Office.js cannot expose, and the codebase is stable and rarely changes. Outside those conditions, Office.js is the better choice.
Should I migrate my VSTO add-in to Office.js?
If your users are on or moving to Mac, Office on the web, or the new Outlook for Windows, plan the migration now. If the add-in is stable, Windows-only, and rarely changes, migration can wait — but should be on the roadmap.
What's the main risk of staying on VSTO?
Platform lock-in. VSTO add-ins cannot reach Mac, Office on the web, or mobile. The new Outlook for Windows does not load them at all. As Microsoft 365 adoption grows, the gap between where users are and where VSTO works will widen.
Keep VSTO where it works; move everything new to Office.js
VSTO add-ins are not dead, but they are a specialist tool now rather than the default. Use them only where deep Windows-desktop access is non-negotiable, and move strategic add-ins to Office.js for reach and lower maintenance. Orfys advises on and executes both.