gg
Home › Excel macros

What is actually inside your macro workbook

Drop in a spreadsheet with macros. This reads it on your own device, tells you everything that is in there — every macro, how many lines, what is hidden — and converts up to three of them to Python, in full. Nothing is uploaded, there is no sign-up, and it costs nothing.

Your workbook

Why three, and why whole ones

It converts three complete macros rather than the first few hundred lines of everything. Half a converted Function will not run, cannot be shown to anyone, and tells you nothing about whether the job is possible. Three that work is something you can read, test, and forward.

The macros it picks are the ones that prove the point — the ones using the parts of VBA a careless conversion gets wrong.

What it will not do

It will not guess. Where a macro uses something that cannot be converted faithfully — a GoTo jump, file I/O, or a parameter passed ByRef that the macro writes back to — it says so, names the line, and converts nothing. Every one of those is listed with its reason.

It converts; it does not prove. Nothing here runs your original and the translation side by side and checks that they agree. That evidence is the whole point of the paid work, and this page does not pretend to it.

A note about protected projects

If your VBA project has a password on it, the macros are still readable here. That password stops Excel's editor from displaying the code; it does not encrypt it. Worth knowing if you had assumed otherwise — it is a property of the file format, not something this tool defeats.

Frequently asked

Does my workbook get uploaded?

No. It is read in your browser, on your machine, by code compiled into this page. There is no server to send it to. That matters for a spreadsheet holding real figures, which is usually exactly what these are.

Why Python?

Because it is readable by people who are not VBA programmers, it runs anywhere without Excel, and it can be tested. The converted code calls a small runtime that reproduces VBA's own arithmetic — integer division, Mod, CInt rounding — so it computes what Excel computed rather than what Python would.

What happens to the other macros?

They are listed, with the line and the reason each one stopped. That list is the scope of the real job.

What does the full job involve?

Converting everything, then running both versions side by side on your own data until they agree, and handing you the evidence that they do. Lazarus Systems does that — same people, different site.