Brainfuck Decoder
Execute Brainfuck code and unpack JSFuck esoteric payloads.
Output appears here as you type — decoded on your device.
Input is processed on your device. Nothing you paste is sent anywhere.
What is the Brainfuck Decoder?
Brainfuck is an esoteric programming language with only eight instructions operating on a memory tape, and an interpreter runs that code to produce its output — usually the hidden message a puzzle encoded as Brainfuck.
Brainfuck's entire instruction set is > < + - . , [ and ]. They move a data pointer along a byte tape, increment or decrement the current cell, output or input a character, and loop while the current cell is non-zero. Everything else in a Brainfuck file is a comment, which is why these programs look like punctuation soup.
It is Turing-complete despite the minimalism, which makes it a favourite for code golf and for CTF challenges where a message is hidden as a program that prints it. Running the code is the only reliable way to read it — static analysis of Brainfuck is a losing game.
JSFuck is the same idea in JavaScript: any program can be written using only []()!+ by exploiting type coercion. The output looks like thousands of brackets, and evaluating it is what reveals the payload — which is also why it shows up in obfuscated malicious scripts.
Brainfuck Decoder at a glance
- Instructions
- > < + - . , [ ] — eight in total
- Memory
- A tape of byte cells with a movable pointer
- Turing-complete
- Yes, despite the eight instructions
- JSFuck alphabet
- Only [ ] ( ) ! +
How to use the Brainfuck Decoder
- 1Paste the Brainfuck program — comments and whitespace are ignored.
- 2Run it and read whatever the program writes to output.
- 3For very long loops, expect the interpreter to cap execution to stay responsive.
When you would reach for it
- Extracting the flag from a Brainfuck-encoded CTF challenge.
- Understanding how a minimal Turing-complete language works.
- Unpacking a JSFuck-obfuscated script to see what it really does.
Brainfuck Decoder — frequently asked questions
Last reviewed · questions or corrections: contact@decoder.tools