There are two limits, because there are two ways to run an audit.
Saved audits: 60 MB
When you are signed in and upload a bulk file, the file is stored so the audit can be saved to your history. Those uploads top out at 60 MB.
In-browser audits: 150 MB
The in-browser audit at https://sheets.adbadger.com/local reads files up to 150 MB. It runs entirely on your own machine. Nothing is uploaded and no account is needed, so it has room for bigger files. It is the same audit and the same report, but the result lives in that browser tab rather than in your history.
If you drop a file between 60 MB and 150 MB on the upload page, The Badger tells you so and points you to the in-browser audit.
Over 150 MB
Tighten the date range. Re-export the bulk file from Amazon for the last 60 to 90 days and drop it again. Most of the size in a big export is search term rows, so a shorter window shrinks the file quickly.
Business Reports: 3.5 MB
The optional Business Report you can add for organic insights must be a CSV or TSV under 3.5 MB. If yours is bigger, export a shorter date range from Seller Central.
A note on memory
Large files are parsed in your browser, which takes real memory. If a big file stalls, close other heavy tabs and try again. If a saved audit fails with a message about exceeding the processing time or memory limit, run the same file through the in-browser audit instead.
Files refused below the limit
A bulk file is a zip, and one sheet inside it can be many times bigger than the file. When a single sheet would unpack to more than a browser can hold in one piece, a bit over half a gigabyte, The Badger refuses the file up front and tells you the sheet size and the date range it came from. This happens with long date ranges on very large accounts, sometimes well under the 60 MB and 150 MB limits, and it is the honest answer: the alternative is a report computed on whichever sheets happened to fit. The fix is the same as for an oversized file. Export the same account for 30 days or fewer and drop it again.