.NET Assembly Viewer
See how a .NET assembly you own or have the right to inspect is built: its version, the assemblies it uses, and every type and member. Free, with no sign up. Your file stays in this browser; nothing is uploaded.
Or drop it here.
To see its sections, imports and exports, open it in the binary inspector.
This assembly defines no types.
Details
Referenced assemblies
It references no other assemblies.
Native libraries it calls
Assembly attributes
Metadata streams and tables
| Stream | File offset | Size |
|---|
| Number | Table | Rows |
|---|
Text in the code
What an assembly's structure can tell you
- Which .NET version a library targets, and which other assemblies it needs to load.
- What a library offers: its public types, methods and properties, before you reference it.
- Whether it calls native Windows libraries, and which text it carries, such as web addresses.
- Its exact version and public key token, to match it against a project's references.
Open only files you own or have the right to inspect. This page reads structure only; it does not run, change or unlock anything.
How to use this tool
Pick a .NET .dll or .exe you own or have the right to inspect, or try the sample. Open a namespace and a type on the tree, click a member to read its details, and search by name.
Frequently asked questions
Is my file uploaded?
No. The page reads the file's headers and metadata inside your browser and makes no network call with it.
Which files can it open?
Any .NET assembly: a .dll or .exe built for .NET, .NET Framework, .NET Standard or Mono, 32-bit or 64-bit. If the file is a Windows program but not .NET, the page says so and points you to the binary inspector.
Does it show the source code?
No. It shows the structure: namespaces, types, fields, methods with their parameter and return types, properties and events, plus where each method's compiled code sits and how big it is. It does not turn compiled code back into source.
What is the public key token?
A short ID made from the assembly's public key, the last 8 bytes of its SHA-1 hash. Other assemblies use it to refer to this one. The page works it out from the key; it does not check the signature.
Where does the target framework come from?
From the TargetFramework attribute the build tools write into the assembly, such as .NETCoreApp,Version=v8.0. Older assemblies may not have one, and then the page says it is not stated.
Why does a .NET app read as not .NET?
A single-file .NET app starts with a small native launcher, and its .NET parts are packed inside. The launcher has no .NET header, so the page reports a native Windows program.