: Only decompile software you have the legal right to inspect or modify.
First, we must understand what a Python executable actually is.
The techniques described in this article are most legitimately applied when you, as a developer, are looking to recover your own abandoned work. As one developer eloquently put it: "千万不要用这套流程去逆向别人的程序！"—Never use this process to reverse-engineer someone else's program!
Getting your code back takes two main steps. First, you unpack the EXE file. Second, you turn the unpacked files back into readable text. Step 1: Unpack the EXE File
At the surface, the process looks procedural: run tools, extract resources, decompile bytecode, stitch together modules. Beneath that, the real work is interpretive. A decompiled script may produce valid statements but often lacks variable names that once carried meaning, comments that held context, and the architectural sense of why functions were shaped a certain way. The conversion becomes an act of hermeneutics — reading the machine’s silence and reconstructing the missing human voice. convert exe to py
: Use uncompyle6 , which is the standard for older versions.
Using decompilation tools for any of the following reasons is generally considered unethical and illegal:
: Ensure the Python version used to run the decompiler matches the version used to build the original executable.
While the core process works for many cases, it's important to be aware of potential hurdles that can affect success: : Only decompile software you have the legal
When you use tools like , cx_Freeze , or py2exe , they do not compile your Python code into native machine code (like C++ compilers do). Instead, they bundle three things:
You cannot convert an EXE to a clean, original .py file with comments, variable names, and docstrings. However, you can recover the logic and structure of your code using a two-step process: the bytecode with pyinstxtractor , then decompile it with pycdc or uncompyle6 .
: In some cases, local variable names might be lost, but the general logic and function names usually remain intact. Alternative Tools Converting an exe back to .py
: These tools map the Python opcodes back to their original syntax. While variable names are usually preserved, comments and docstrings are lost forever Second, you turn the unpacked files back into readable text
Inside, you will find several .dll files, a .pyc file for the main script, and subfolders like PYZ-00.pyz_extracted containing the bytecode for all imported modules.
If the EXE was "obfuscated" (protected) before compilation, the resulting code may look like gibberish.
Use a tool like PyInstXTractor (PyInstaller Extractor) to unpack the .exe . : python pyinstxtractor.py your_file.exe .
You can extract from most PyInstaller-packaged EXEs, but you'll never get the original formatting, comments, or imports exactly as they were.
PyInstaller executables contain a structured archive called that holds all the bundled files, along with a PYZ archive for Python modules and packages. When you use pyinstxtractor or similar tools, you're essentially unpacking these archives to retrieve the original .pyc files.