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
Analyze .NET EXE and DLL assemblies, view readable C# code, and export project files.
Choose filesDrop a file here, or click to choose
.exe · .dll
Max 2 MB
Upload limits: guest 2 MB, member 4 MB, advanced 10 MB, pro 40 MB.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
A managed .NET .dll or .exe usually retains metadata for types, members, inheritance, dependencies, and method bodies as intermediate language. The decompiler turns these structures into readable C# for inspecting implementation and call paths.
The downloadable project ZIP reconstructs runtime logic but may not include original comments, formatting, file organization, build settings, dependency versions, signing keys, or environment configuration. VB.NET and F# assemblies are also rendered as C#.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Select an authorized managed .NET .dll or .exe.
Upload a file up to 5 MB; it is processed in an isolated temporary server workspace without requiring a local Java or .NET runtime.
Preview the recovered namespaces, types, and files, then download the project ZIP.
Review fields, constructors, methods, calls, returns, exception paths, and dependency clues.
Tip: Start with a simple public method when reviewing an optimized build.
Use cases
See how the tool fits into real work and everyday tasks.
Inspect interfaces, type boundaries, and workflows when source code is unavailable.
Compare members, calling conventions, and exception sources across dependency versions.
Trace relevant code paths and compare findings with logs and configuration.
Q&A
Find concise answers to common questions and confusing cases.
Compilation removes comments, whitespace, and some names, while optimization can reshape expressions and control flow. The result represents reconstructed logic rather than the original source.
No reliable reconstruction is possible. The export uses C# and does not restore the original syntax or project structure.
The assembly may be native, obfuscated, packed, trimmed, protected, missing dependencies, or using unsupported constructs. Confirm the file type and, if available, try a smaller unpacked sample you own.
Notes
Review scope, result limitations, and important precautions before use.
Analyze only assemblies you own or are explicitly authorized to inspect. Check applicable licenses, contracts, and organizational policies before processing third-party software.
Files are processed by the server in a temporary workspace that is cleared when the task ends. Do not upload credentials, private keys, customer data, internal addresses, or undisclosed business logic, and protect downloaded ZIPs.
Results may be incomplete, and the exported project may not compile or preserve original build conditions. Verify important findings against authorized source, build artifacts, and symbols rather than treating inferred names as facts.
Related
Discover related tools, collections, and available API capabilities.