We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Upload Python .pyc or .pyo bytecode files and attempt to recover readable, approximate .py source code.
Choose filesClick or drag to upload .pyc, .pyo files
Supports multiple files, up to 256 KB per file
Max 256 KB
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
A .pyc file contains Python bytecode used by the interpreter as a compiled module cache. This tool accepts .pyc and .pyo files and attempts to turn each into readable Python-like source. A successful result can help you inspect logic when the original .py file is unavailable. It is a reconstruction, not a restored copy of the author’s source: comments and original formatting are not stored in bytecode, and names or code structure may be incomplete or altered.
Python documents bytecode caches as an import-system detail, and their contents vary with interpreter versions. See the Python import system documentation for the role of cached bytecode.
Choose individual .pyc or .pyo files, up to 256 KB each. Multiple selected files are queued and processed one at a time. For each file, the page reports a processing status; successful output can be viewed and downloaded as a .py file. No Python-version selector is provided. Whether a file can be reconstructed depends on its bytecode format, integrity, and the decompiler’s current support.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Select one or more small .pyc or .pyo files. Other extensions are not added to the queue.
Run decompilation and follow each file’s status. A failure on one file may have a different cause from a failure on another.
Open successful output, compare important logic with trusted references or tests, then download the generated .py file if it is useful.
Use cases
See how the tool fits into real work and everyday tasks.
If a project has a compiled module but its source file is missing, use the output as a starting point for understanding the module’s likely logic.
For maintenance or security review, inspect reconstructed code alongside project records and other evidence. Do not treat a decompilation result alone as proof of the original author’s intent.
Q&A
Find concise answers to common questions and confusing cases.
No. Compilation discards or changes source details, so the result is an approximation and may need correction.
Its bytecode version may not be supported, or the file may be incomplete or damaged. The tool does not let you select a Python version to force a match.
This page accepts .pyc and .pyo files. It does not accept archive or executable formats as substitutes.
Notes
Review scope, result limitations, and important precautions before use.
Only analyze code you own or are authorized to inspect. Uploaded bytecode is sent to a remote processing service, so do not submit confidential or regulated material unless you are permitted to share it that way. Treat reconstructed source as unverified: test consequential behavior and preserve a separate copy of the original bytecode.
Related
Discover related tools, collections, and available API capabilities.