Tiny Online Tools
One pass over a whole mailbox
Saving attachments one message at a time is fine for three messages and hopeless for three hundred. Drop in a folder of .eml files, a couple of Outlook .msg files and a mailing-list .mbox together; every message in every file is opened, every attachment is decoded, and the result is one list.
The format of each file is decided from its bytes, not its name. A .msg that someone saved as .eml, and a mailing-list archive that arrived as .txt, both open correctly. A file that is none of the three — a PST, a calendar, a ZIP — is reported against its own name and the rest of the batch carries on.
Inline images are told apart properly
A signature logo is not something you wanted to save. Telling it from a real attachment cannot be done by reading Content-Disposition, because Outlook and Gmail both mark the images their own HTML embeds as attachment. What this tool checks instead is whether the HTML body actually contains cid: followed by that part's Content-ID. If it does, the part is embedded artwork; if it does not, it is a file the sender meant you to keep.
Identical copies, collapsed
In any list archive the same footer image appears in hundreds of messages. Every attachment is fingerprinted by its content, so exact repeats are marked and can be hidden with one toggle — and the number collapsed is reported rather than quietly swallowed. It is a fingerprint over the bytes, not a claim about the file's identity.
The ZIP is built to be unpacked
Each source file gets its own folder, and every name is prefixed with its position, so two messages that both attached invoice.pdf do not overwrite each other. Path separators and the characters Windows refuses are stripped from names before they go in. A manifest.csv travels inside the archive listing every file with the message and subject it came from, because after unpacking that question has no other answer.
What you get out
Exactly the bytes that were in the message, decoded from base64 or quoted-printable and written unchanged. Nothing is re-encoded, resized or renamed beyond what a filesystem requires.
Privacy
Every file is read in your browser. No message, no attachment and no filename is ever uploaded.