Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

uncompyle6

github.com

  • Free plan
  • Windows
  • macOS
  • Linux
  • Self-hosted
7.7 Club score Visit github.com

What uncompyle6 is

uncompyle6 is a free, GPL-3.0-licensed tool that translates Python bytecode into equivalent Python source code. It runs from the command line on compiled `.pyc` or `.pyo` files, and can also deparse code fragments or provide source information around a bytecode offset. That fragment capability is used in trepan debuggers to display source during runtime and can add stack-trace detail beyond a line number. The README says it accepts bytecode from Python 1.0 through 3.8, Dropbox Python 2.5 bytecode, and some PyPy bytecode. Its `--syntax-verify` option checks decompiled syntax when paired with the corresponding bytecode version. The project identifies control-flow handling as a major challenge and notes that some incorrect decompilations may be detected and reported. It does not handle obfuscated code, Cython, or MicroPython, and cannot directly decompile Py2EXE executables. The README says Python 3.7 and 3.8 support is generally better in the related decompile3 project. For Python 3.11 and later, it directs users to install with `pip install uncompyle6`; earlier Python versions use a file from GitHub Releases. The package is classified as operating-system independent, and its intended audience is developers.

Who it suits

uncompyle6 suits developers who need to inspect supported Python bytecode or display source fragments during debugging. It may be useful when working with compiled `.pyc` or `.pyo` files that fall within its supported inputs.

Good to know, and what to watch

  • Translates Python bytecode into equivalent source
  • Can deparse fragments and locate source around bytecode offsets
  • Command-line support for `.pyc` and `.pyo` files
  • Free and GPL-3.0 licensed
  • Does not handle obfuscated code, Cython, or MicroPython
  • Cannot directly decompile Py2EXE executables
  • Control-flow handling can produce incorrect decompilations
  • Python 3.7 and 3.8 support is generally better in decompile3

Open-source software

Free

Open source

Getting started

  1. Open the uncompyle6 GitHub website
  2. Install with pip install uncompyle6 on Python 3.11 or later
  3. For older Python versions, obtain the installation file from GitHub Releases
  4. Run uncompyle6 against compiled .pyc or .pyo files
  5. Use --syntax-verify with the matching Python bytecode version

Limits to check

The tool does not support obfuscated code, Cython, MicroPython, or direct Py2EXE decompilation. Control-flow issues can lead to incorrect decompiled output.

The verdict

uncompyle6 offers bytecode decompilation and fragment-level source information for developers. Its input limits and control-flow challenges make it important to check whether a particular file and Python version are supported.

Questions people ask

What does uncompyle6 do?

It translates Python bytecode into equivalent Python source and can deparse code fragments or show source information around a bytecode offset.

Is uncompyle6 free?

Yes. It is free, open-source software under the GPL-3.0 license.

Which bytecode versions does it accept?

The README describes Python 1.0 through 3.8, Dropbox Python 2.5 bytecode, and some PyPy bytecode.

Which operating systems can run it?

Linux, macOS, Windows, and self-hosted use are listed; PyPI classifies it as operating-system independent.

How is it installed?

Python 3.11 and later use pip install uncompyle6 from PyPI. Earlier Python versions use a file from GitHub Releases.

What the maker publishes

Bytecode versions
The README says it accepts bytecode from Python 1.0 through 3.8, plus Dropbox Python 2.5 bytecode and some PyPy bytecode. source
Command line
The README shows running `uncompyle6` on compiled Python `.pyc` or `.pyo` files. source
Debugger use
The maintainer says fragment deparsing is used in trepan debuggers to show source fragments at runtime. source
Debugging use
The maker says fragment deparsing can help show stack traces with more detail than a line number and is used in the maker’s trepan debuggers. source
Fragment decompilation
It can deparse code fragments and provide source information around a bytecode offset. source
Installation
For Python 3.11 and later, the README instructs users to install from PyPI with `pip install uncompyle6`. source
Intended audience
The package metadata classifies its intended audience as developers. source
Intended audience
PyPI lists developers as the intended audience. source
Known limitation
The README identifies control-flow handling as a major decompilation problem and says erroneous decompilations may sometimes be detected and reported. source
License
The repository identifies the project as GPL-3.0 licensed. source
Older Python installation
For Python versions before 3.11, the README directs users to install from a file in the GitHub Releases section. source
Operating systems
PyPI classifies the package as operating-system independent. source
Purpose
uncompyle6 translates Python bytecode into equivalent Python source code. source
Support
The maintainer says bug reports may take a while to receive attention and that sponsoring or supporting the project can prioritize issues. source
Syntax verification
The `--syntax-verify` option checks decompiled syntax when used with the matching Python bytecode version. source
Unsupported inputs
The README says it does not handle obfuscated code, Cython, or MicroPython, and cannot directly decompile Py2EXE executables. source
Version caveat
The README says Python 3.7 and 3.8 support is generally better in the related decompile3 project. source
What it does
uncompyle6 translates Python bytecode back into equivalent Python source code. source

Checked against the maker's pages on 8 Oct 2026.