Erlang & Elixir BEAM Decompiler Online
Recover Erlang source from retained debug information, or inspect module metadata and BEAM instructions.
Open a BEAM module
Upload an Erlang or Elixir .beam file above. You can also upload a supported archive and open a BEAM module inside its results. Files are recognized by their BEAM container signature.
Open source.erl when source recovery succeeds, disassembly.txt for available VM instructions, or beam.json for the module name, exports, imports, chunk inventory and recovery statuses. Download individual files or the result ZIP. Your original module remains available.
Can I recover Erlang source?
Readable abstract or supported debug information can produce Erlang source. Stripped, encrypted, incompatible or unsupported debug data may prevent source recovery. Available metadata and disassembly remain useful even when source is unavailable. Disassembly also depends on whether the installed OTP decoder supports the bytecode version.
What does an Elixir module produce?
Supported Elixir debug information produces an Erlang representation of the Elixir module. This is an .erl file, not the original .ex source. Original macro and defguard syntax, comments and formatting are not reconstructed.
Limits and compatibility
Inspection accepts modules up to 32 MiB. Term decoding, decompression, atom counts, processing time and output sizes are bounded. Listings can be truncated at 8 MiB, with an explicit status. Supported debug backends are Erlang abstract code and the installed Elixir backend. No password or encryption-key entry is available.
The uploaded module is inspected without running it. Results identify what was recovered and why other representations are unavailable.