.erl

What is a .erl file?

Erlang is the language that keeps phone networks and WhatsApp running — built for fault tolerance and massive concurrency.

Use caution
Type Code
By Ericsson (Joe Armstrong et al.)
MIME text/x-erlang

Drop any file to identify it

No upload. No signup. No sending your file halfway across the internet.
We tell you what it is, right here in your browser.

What is it

Erlang was designed inside Ericsson in the 1980s to program telephone switches — systems that absolutely cannot go down. The language's core features reflect this: lightweight processes that crash independently, supervisors that restart failed processes automatically, and hot code upgrades that update running systems without a single dropped call.

WhatsApp handled 900 million users with a team of 50 engineers, largely because Erlang's concurrency model scales almost linearly. RabbitMQ, CouchDB, and ejabberd are built on Erlang. The language proves that boring, reliable technology can run the world's most demanding systems.

Erlang's syntax is unusual — influenced by Prolog, with pattern matching, atoms, and a period-terminated clause structure that surprises newcomers. The OTP (Open Telecom Platform) framework provides battle-tested patterns for building fault-tolerant systems. Most new projects in this ecosystem choose Elixir (modern syntax, same runtime), but Erlang itself remains essential for understanding and maintaining existing systems.

Technical details
Full Name
Erlang Source
MIME Type
text/x-erlang
Developer
Ericsson (Joe Armstrong et al.)
Magic Bytes
N/A
Safety
.erl requires caution. Source code file. Safe to read.
What opens it
VS Code (+ Erlang extension)
FREE Windows / Mac / Linux
Any text editor
FREE Windows / Mac / Linux
FAQ
Is Erlang still relevant?
Absolutely. WhatsApp, RabbitMQ, CouchDB, and many telecom systems run on Erlang. New projects often choose Elixir (same runtime, modern syntax), but Erlang itself is actively maintained and deeply embedded in critical infrastructure.
What makes Erlang fault-tolerant?
Lightweight isolated processes, supervisor trees that restart crashed processes, hot code loading for updates without downtime, and a 'let it crash' philosophy where errors are handled by restarting clean rather than defensive coding.
Related formats