A Free Alternative to Power Automate for Splitting Excel Files

Power Automate (formerly Microsoft Flow) can split an Excel workbook into separate files. It also requires: a Microsoft 365 license, the file to live in SharePoint or OneDrive, a 15-30 minute flow-building session with "List rows," "Apply to each," and "Create file" actions, and familiarity with Power Automate's retry/throttling quirks.

If you're splitting workbooks occasionally, that overhead is ridiculous. Our free browser sheet splitter handles the same job in 30 seconds. Drop the file, download the sheets, move on. Power Automate is still the right tool for scheduled high-volume automation — but not for "I need to split this one workbook right now."

What Building the Flow Actually Takes

1. Microsoft 365 license. Power Automate is bundled with most M365 plans but not all. Personal plans often don't include it.
2. File in SharePoint or OneDrive. Power Automate's Excel connectors don't operate on local files directly. Upload first.
3. The workbook must be stored as a Table. Raw data in cells doesn't work with the Excel Online connector — you have to format your data as a table first (Ctrl+T in Excel).
4. Build the flow: Manually trigger, List rows from table, Apply to each (for iterating through distinct values or sheets), Create file (to write each split as a new .xlsx in SharePoint).
5. Handle throttling. The Excel Online connector has API call limits. Large workbooks trip them.
6. Test. Flows often fail the first time because of path issues, permission scope, or table naming.

Total time: 15-30 minutes for someone who knows Power Automate. Much longer for a first-timer.

When Power Automate Is the Right Tool

Three legitimate reasons to use Power Automate instead of a browser tool:

• Daily or hourly automation. File lands in SharePoint nightly → flow runs → splits → emails each file to the right recipient. A browser tool can't run unattended.
• Split is part of a bigger workflow. Split workbook → loop through files → run data validation → write results to Dataverse → notify Teams channel. Power Automate chains all these steps.
• Corporate environment with Power Automate infrastructure. You're already using flows; adding one more fits the existing governance, logging, and monitoring.

For any of those, the 20-minute flow setup pays off over the lifetime of the automation.

Sell Custom Apparel — We Handle Printing & Free Shipping

When Power Automate Is Overkill

• You have one or two workbooks to split today.
• You don't need to schedule anything.
• You don't have a Microsoft 365 business license (e.g., you're on Microsoft 365 Personal or have no Office at all).
• The file is on your local drive, not SharePoint.
• You're not already deep in Power Automate.

For any of those, the browser tool is 30 seconds end to end.

Side-by-Side on Time and Cost

Scenario	Power Automate	Browser Tool
First-time setup	15-30 min + license cost	30 seconds, free
Subsequent one-off splits	2-5 min (click through flow)	30 seconds
Scheduled automated splits	Perfect fit	Not supported
Local file (not in SharePoint)	Requires upload first	Drag from desktop
Split across multiple file types	Needs separate connectors	Works on .xlsx, .xls, .ods natively
Works offline	No	Yes (after first load)
Shareable with non-technical team	No — needs flow permissions	Yes — just a URL

Using Both Together

The two aren't mutually exclusive. A realistic hybrid pattern:

• Power Automate for scheduled splits of files that land in SharePoint nightly.
• Browser tool for ad-hoc splits during the day when a colleague emails you a workbook and you need the January tab in 30 seconds.

Trying to force Power Automate to handle every one-off need is what burns the time. Trying to replace scheduled automation with a manual browser tool is what creates fragile processes. Match the tool to the cadence.

Frequently Asked Questions

Can Power Automate run without Microsoft 365?

There's a Power Automate Free tier with limited connectors and no premium features. The Excel Online connectors needed for workbook splitting require a paid Microsoft 365 or Power Automate Premium license.

Will the browser tool work in an enterprise environment that blocks consumer cloud tools?

It depends on your firewall policy. The tool is a static HTML page with client-side JavaScript — no server calls during operation. Most corporate firewalls allow this; some lock it down. Check with IT if unsure.

Can I use the browser tool inside a SharePoint-native workflow?

Not directly — a browser tool requires a human to drop a file. For automation inside SharePoint, you need Power Automate or a custom script.

Is it possible to trigger the browser tool from Power Automate?

No — browser tools need a user action (drag-and-drop). You could write a Power Automate flow that calls a server-side API; the browser tool isn't that.

What about Logic Apps / Azure Automation?

Same trade-offs as Power Automate but for Azure-native workflows. Good for scheduled automation; overkill for one-offs.