Hi everyone, I build embedded firmware, and figuring out what's eating your flash and RAM usually means squinting at nm and size output, or wiring up a linker map parser. memprobe makes it visual. Drop an ELF in the browser and you get flash and RAM broken down by section, symbol, and source file, plus a treemap, a call graph, and warnings that name the exact compiler flag to cut the bloat. No signup to try it. The same analysis runs from a CLI and a GitHub Action, so you can gate build size in CI and get a size-diff comment on every pull request. The CLI and Action are open source (MIT), and your binary never leaves your machine when you use them. Free to use, and free for open source. I would love feedback, especially from anyone fighting flash exhaustion.

memprobe.dev

See where your firmware's flash and RAM go

See where your firmware's flash and RAM go