Zxilly/go-size-analyzer

What is it?

Key features

• 01Analyzes ELF, Mach-O, PE and experimental WebAssembly binaries.
• 02Breaks down size by package, standard library, vendor dependency and section.
• 03Outputs text, JSON, HTML and SVG treemap reports.
• 04Provides an interactive web interface and a terminal UI.
• 05Compares two binaries or saved JSON results in diff mode.

Use cases

• Finding which dependencies inflate a Go service or CLI binary.
• Tracking binary size changes between Go toolchain versions or commits.
• Sharing an interactive size treemap of a build with teammates over a network.
• Checking whether debug sections or symbols are a major part of a release binary.

Quick start

1. 1

   Install with Go

   go install github.com/Zxilly/go-size-analyzer/cmd/gsa@latest
2. 2

   Start the web interface on a compiled Go binary

   gsa --web golang-compiled-binary

Things to know

• !Licensed under AGPL-3.0, a copyleft license that requires sharing modified source code when served over a network.
• !Building from source requires Go 1.27 or later.
• !Analysis of stripped binaries may be inaccurate.
• !The WebAssembly version in the browser is much slower than the native version.

In collections

Topics

FAQ

What is go-size-analyzer?

A command-line tool that breaks down the size of compiled Go binaries by package, section and symbol, with text, JSON, HTML, SVG, web and terminal UI output. go-size-analyzer answers the question of what makes a compiled Go binary large. It parses ELF, Mach-O, PE and experimental WebAssembly binaries and attributes their size to packages (including the standard library and vendored dependencies) and to binary sections such as .rodata, .gopclntab and DWARF debug data.

Is go-size-analyzer free to use? What license does it have?

go-size-analyzer is open source under the AGPL-3.0 license. Check the license terms before using it in commercial products.

Is go-size-analyzer still maintained?

Actively maintained. The last commit to go-size-analyzer was on Nov 4, 2026.

What can I use go-size-analyzer for?

Finding which dependencies inflate a Go service or CLI binary. Tracking binary size changes between Go toolchain versions or commits. Sharing an interactive size treemap of a build with teammates over a network. Checking whether debug sections or symbols are a major part of a release binary.

How do I install go-size-analyzer?

Install with Go: go install github.com/Zxilly/go-size-analyzer/cmd/gsa@latest Start the web interface on a compiled Go binary: gsa --web golang-compiled-binary

Where can I get go-size-analyzer?

The source code and installation instructions are on GitHub: https://github.com/Zxilly/go-size-analyzer