Excel VBA Limitations in 2026: What Macros Still Can't Do Online

TL;DR: As of 2026, VBA macros do not run in Excel for the web or the Excel mobile apps - at all. Microsoft's replacement, Office Scripts, requires rewriting your automation in TypeScript and still can't do UserForms, event-driven workflows, or external connections. If a macro-driven workbook needs to work in a browser, your realistic options are keeping everyone on desktop Excel, rebuilding in Office Scripts, or converting the tool to a custom web application that keeps the exact logic and drops the Excel dependency.

Macros are the single biggest reason business workbooks stay chained to desktop Excel. The file that runs your quoting, scheduling, or reporting probably has years of VBA behind its buttons - and the moment anyone opens it in a browser or on a phone, all of that stops working. Every year teams check whether Excel Online finally runs VBA. This is the current, honest answer.

The Short Answer: Macros Do Not Run in Excel Online

Excel for the web has never executed VBA, and in 2026 it still doesn't. There is no partial support, no compatibility mode, and no "enable macros" button to find. Microsoft's own documentation on browser vs desktop differences is plain about it: macro-enabled workbooks open in the browser, but the macros in them cannot run, be created, or be edited there.

This isn't Microsoft being slow. It's architectural, and understanding why makes the options clearer.

Why VBA Can't Run in a Browser

VBA is not just a scripting language - it's a 30-year-old automation layer built on COM, the Windows component technology that lets programs control each other on a local machine. VBA macros assume they can touch the filesystem, drive other Office applications, call Windows APIs, and manipulate the Excel application object itself. A browser tab, by design, can do none of those things: it's a security sandbox with no access to your machine.

Porting VBA to the web would mean either breaking that sandbox (a security non-starter) or rebuilding the entire COM object model in the cloud (which Microsoft chose not to do). Instead, Microsoft built a new automation platform from scratch - more on Office Scripts below.

What Actually Happens When You Open an .xlsm in the Browser

If your team is seeing "macros not working" in Excel Online, this is the pattern. The workbook opens and looks normal. Then:

Buttons do nothing. Form controls and shapes wired to macros render as static decoration. A click either does nothing or shows an error that macros can't run in this version of Excel.

UserForms never appear. Any dialog-driven workflow - data entry forms, wizards, pickers - is simply gone. There is no browser equivalent of a VBA UserForm.

Event automation is dead. Workbook_Open routines that refresh data, Worksheet_Change handlers that validate entries, Before_Save hooks that enforce rules: none of them fire. The workbook silently stops protecting itself, which is more dangerous than an obvious error.

The formulas still calculate. This is what fools people. Cell formulas are fully supported in the browser, so the workbook seems 90% alive - until someone needs the 10% that was automated, which in most business tools is the part that mattered.

Office Scripts: What Microsoft Offers Instead - and What's Missing

Office Scripts is Microsoft's browser-era automation for Excel: scripts written in TypeScript, stored in the cloud, run from a button or a Power Automate flow. For simple record-a-task automation - formatting, data cleanup, moving rows between sheets - it genuinely works, and it runs in desktop Excel too on current Microsoft 365 plans.

But calling it a VBA replacement oversells it. As of August 2026, the gaps that matter:

Nothing converts automatically. There is no VBA-to-Office-Scripts migrator. Every macro must be rewritten by hand in a different language, and Microsoft's own VBA-to-Office-Scripts comparison is a long list of "not supported."

No custom dialogs. UserForms have no equivalent. A script can prompt nothing more than what a worksheet cell can capture.

No workbook events. Scripts run when a person clicks or a Power Automate flow triggers them. Change-driven and open-driven automation doesn't exist.

No outside connections. Office Scripts can't reach other applications, local files, ODBC sources, or COM add-ins. External calls are limited to web APIs, with restrictions, and not when run through Power Automate.

Licensing. Office Scripts requires a qualifying Microsoft 365 business or education plan for everyone who runs them - relevant if your workbook's users include clients or field staff who don't have one.

The Mobile Apps: Even More Limited Than the Browser

The Excel mobile app's limitations compared to desktop go beyond macros, but macros top the list: the iPhone, iPad, and Android apps cannot run VBA at all, same as the browser. Beyond that, pivot tables are view-only (you can't create or modify them), most desktop data tools are absent, and a workbook wider than a few columns fights the screen. If your estimators or inspectors need the company calculator in the field, the mobile app is where that plan goes to die - a 12-column macro workbook on a 6-inch screen is unusable twice over. We covered the full browser-and-mobile gap list in our Excel Online vs desktop comparison.

Where VBA Workbooks Stand in 2026

Capability comparison, current as of August 2026:

Capability	Desktop Excel	Excel for the web	Office Scripts	Custom web app
Runs your existing VBA	Yes	No	No - full rewrite in TypeScript	Logic recreated once in JavaScript, verified against the original
Custom forms and dialogs	UserForms	No	No	Any interface you want - it's a web page
Event-driven automation	Yes (Workbook_Open, Change, etc.)	No	Button or Power Automate only	Yes - validation and logic run on every input
Works fully on phones	No	Partially, macros excluded	No mobile authoring	Yes - responsive by design
What users need	Excel license + install	Microsoft account	Qualifying Microsoft 365 plan	A browser
Your logic stays private	No - anyone with the file can read the code	No	Partly - scripts are shareable assets	Yes - logic runs on your server or minified in the app

Your Real Options for a Macro Workbook That Needs to Live Online

Option 1: Keep everyone on desktop Excel. Legitimate when the tool is internal, every user has a license, and nobody needs it on a phone or in the field. The cost is invisible but real: every new user needs Excel installed, version sprawl returns, and clients can never touch the tool directly.

Option 2: Rebuild in Office Scripts. A fit when the automation is simple (formatting, data shuffling), everyone who'll run it has a qualifying Microsoft 365 plan, and you have someone comfortable writing TypeScript. Poor fit for anything with UserForms, event handlers, or external connections - which describes most serious VBA tools.

Option 3: Convert the tool to a web application. When you want to convert Excel to web with the VBA logic intact, this is the route that actually carries the macros over: formulas and VBA procedures get translated to JavaScript once, outputs verified side by side against the original workbook, and the result is a branded web page that works for anyone, on anything, with no license and no macro warnings. We've documented exactly how VBA macros convert to JavaScript, and our Excel VBA to web application service covers scope, pricing ($500-5,000 one-time), and timelines.

The pattern shows up even in small tools. A craft supplies company's fabric calculator was a downloadable spreadsheet whose validation logic required customers to enable macros - so most customers emailed support instead. As a web app the same logic runs instantly on the product page, no download, no macro prompt, no Excel at all.

The Question Behind the Question

"Why won't my macros run online" usually isn't really about macros. It's a sign the workbook has outgrown its container: it has real users, real workflows, and real business logic, and it's being distributed on a runtime (desktop Excel) that its users increasingly don't have in front of them. Excel Online can't fix that, and Office Scripts mostly relocates the problem. Our complete guide to converting Excel to a web application walks through every route, cost, and timeline - including the free ones.

Have a macro workbook stuck on the desktop? Send it over - within 24 hours you'll get a free, fixed-price quote for converting it into a web app, including an honest assessment if Office Scripts or staying on desktop is genuinely the better fit for your case.

Frequently Asked Questions

Do Excel macros work in Excel Online?

No. Excel for the web cannot run VBA macros at all. A macro-enabled workbook (.xlsm) opens in the browser and you can view and edit the cells, but every macro, button, and UserForm in it is inert. This has been true since Excel Online launched, and as of 2026 Microsoft has announced no plans to change it.

Can I enable macros in Excel for the web?

There is no setting to enable. Desktop Excel asks you to enable macros because it can run them and wants permission; Excel for the web has no VBA runtime, so there is nothing to switch on. If a tutorial claims to enable macros in the browser, it is describing Office Scripts, which is a different technology requiring your automation to be rewritten in TypeScript.

What is the alternative to VBA in Excel Online?

Microsoft's official alternative is Office Scripts, a TypeScript-based automation platform for Excel on the web. It requires a qualifying Microsoft 365 business or education plan and a full rewrite of your VBA code - nothing converts automatically. For client-facing or business-critical tools, the other route is converting the workbook to a custom web application, which recreates both formulas and macro logic in JavaScript.

Do macros work in the Excel mobile app?

No. The Excel apps for iPhone, iPad, and Android cannot run VBA macros, and they are more limited than Excel Online in other ways too: pivot tables are view-only, most data tools are absent, and multi-column workbooks are difficult to use on a phone screen.

How do I convert an Excel VBA tool to a web application?

A developer translates the workbook's formulas and VBA procedures into JavaScript, rebuilds the interface as a proper web page, and verifies the outputs side by side against the original workbook. The result runs in any browser and on any phone with no Excel license and no macro security warnings. Typical cost for a done-for-you conversion is $500 to $5,000 one-time, depending on the amount of VBA logic involved.