decompiler.com

What is Decompiler.com?

Decompiler.com is a browser-based decompiler that turns compiled software artifacts back into readable source code or extractable assets. You drag a file onto the page, and it attempts to reconstruct the underlying Java, C#, Python, Lua, ActionScript or other code, or unpack the archive so you can browse its contents. It covers a wide range of formats in one place rather than requiring a separate desktop tool for each language.

What you can throw at it

• Java and JVM: .jar, .war, .ear, .class
• Android: .apk, .xapk, .aab, .aar, .apkm, .apks, .dex, .smali, plus Unity asset and C# extraction
• .NET: .exe and .dll back to a C# project (F# and Visual Basic also mentioned)
• Python: .pyc, .pyo, .rpyc, and .rpa archive extraction
• Lua family: .luac, .lub, .luau, LuaJIT
• Flash: .swf back to .fla and resources
• Electron: .asar archive extraction
• Game and other formats: Roblox (.rbxl, .rbxm, .rbxlx, .rbxmx), Hermes (.hbc, .bundle), Source engine (.bsp), GoldSrc/AMX Mod X (.smx, .amxx)

Who it suits

• A developer handed a legacy .jar with no source and needing to see how a method works.
• A security analyst checking what an Android APK or .NET binary actually does before running it.
• A modder extracting assets or scripts from a Unity, Godot, GameMaker, Cocos or Roblox title.
• A student or researcher who wants a quick look without installing a full IDE plugin or reverse-engineering suite.

H3. Trade-offs to weigh Convenience is the draw: no installation, and results you can view or download immediately. Two caveats are worth knowing up front.

First, decompilation is rarely perfect. Reconstructed code often differs from the original — variable names, comments and formatting are typically lost, and obfuscated or heavily optimized builds may not round-trip cleanly. Treat output as a close approximation to read and reason about, not a byte-identical original.

Second, uploading means the file leaves your machine. For proprietary or sensitive binaries, check the site's privacy and terms pages first, or use an offline decompiler instead. The page also notes that an ad blocker can prevent drag-and-drop uploads, so you may need to disable it or use the file chooser.

The site bundles adjacent utilities too — a JAR/APK/WAR/EXE/DLL/DEX diff tool, a JWT decoder, Base64 encode/decode, and a JAR string editor — which are handy when you want to compare two builds or inspect strings without a separate tool.

H3. A practical next step If you are new to this, start with one small, non-sensitive file: a toy .jar or a .pyc you compiled yourself. Confirm the output looks like recognizable source, then move to your real target. For anything confidential, decide between the online route and a local alternative such as GitHub-hosted open-source decompilers before you upload. If you need to compare two versions of the same artifact, the built-in diff tools here can save a step.

How do I decompile an APK file to Java source code using Decompiler.com?

Upload the APK to Decompiler.com, let it process, then download the decompiled output; the site lists .apk, .xapk, .aab, .aar, .apkm, .apks, and .dex files as accepted Android inputs, and describes the result as Java source code plus Unity asset and C# extraction.

Steps

1. Open the site and use the upload area: choose a file or drag your APK onto it.
2. If drag-and-drop fails, an ad blocker is the likely cause — the page itself says to disable it and reload.
3. Wait for processing, then browse the content online or download the decompiled result.

What you actually get

An APK is a compiled package, not a single program. Expect the tool to unpack it into its parts: classes.dex (or several) turned back into Java, plus resources, manifests and, in the Android case, Unity assets and C# if the app was built with Unity. "Back to Java source code" describes the decompiled output, not the original project — comments, formatting and original names are gone.

Practical expectations

• Obfuscated apps (ProGuard/R8) return names like a, b, c. Readable logic, poor structure.
• Kotlin code often appears as Java-shaped output, which can look odd.
• Some methods fail to decompile and appear as raw bytecode or errors.
• If you only need one class, pulling the DEX out first and using the DEX path is faster than the whole APK.

Choosing the right route

A concrete scenario

You want to know how an app builds a signed request. Decompile the APK, search the Java output for HmacSHA256 or the header name, and read the surrounding method. If names are obfuscated, follow the string constants instead — they usually survive.

Next step: if the output is too tangled, try a second tool on the same DEX and compare, since decompilers differ in how well they handle modern bytecode. For a quick sanity check on whether you have the right file, the site also offers Decompiler.com's APK Diff and DEX Diff pages.

Can I decompile a .NET EXE or DLL back to a C# project with Decompiler.com?

Yes. Decompiler.com explicitly supports .NET decompilation of .exe and .dll files back to a C# project, and the page also mentions F# and Visual Basic as source languages it can recover. You upload the artifact through the drag-and-drop area or the file picker, and the result is viewable online or downloadable.

H3 Practical scenario

A common use is inspecting a third-party .NET tool or library when you no longer have the original solution: you upload the DLL, browse the recovered types and methods, then export the project to open it in an IDE. This is useful for debugging, security review, or recovering lost source for code you own.

H3 Things to keep in mind

• Decompiled output is reconstructed, not the original source: comments, formatting, local variable names, and some compiler-generated constructs will differ.
• Obfuscated assemblies can produce hard-to-read or broken output.
• Only decompile software you have the right to inspect; check the license or terms first.
• Large binaries may take longer to process, and the online workflow means uploading your file to a third-party service, which matters for proprietary or sensitive code.

H3 Next step

If you want a desktop alternative for offline work, ILSpy and dnSpy are well-known .NET decompilers, and JetBrains dotPeek is another option. For a quick look without installing anything, start with Decompiler.com and compare the exported project against the original behavior in your IDE.

How can I extract assets and C# code from a Unity game APK on Decompiler.com?

Decompiler.com can do this in one upload: it accepts APK files and, per its own page, supports "Unity game asset and C# extraction" alongside Android decompilation back to Java source. So you do not need to unpack the APK yourself first.

H3 Practical workflow

1. Open Decompiler.com and drop your .apk onto the upload area (or use Choose file). If drag-and-drop fails, the site says an ad blocker is usually the cause — disable it for this page and reload.
2. Let it process, then browse the results. For a Unity build, expect two useful threads: C# code recovered from the .NET assemblies, and asset files from the game's data folders.
3. Download what you need rather than trying to read everything in the browser.

H3 What you can realistically get

• C# code: Unity ships game logic in managed .NET assemblies, which is why the site's ".exe and .dll .NET decompilation back to C# project" capability applies here. You get C# source, not the original project files.
• Assets: textures, audio, models, shaders and similar files bundled in the APK. These come out as the files themselves, so you still need the right viewer for each format.

H3 Trade-offs to expect

• Recovered C# is decompiled output, not the developer's original comments, names or folder structure. Obfuscated games can be much harder to read.
• Some assets are packed in Unity's own bundle formats and may need a dedicated Unity asset tool after extraction.
• Very large APKs take longer and may hit upload limits; splitting the APK is not usually practical, so try the whole file first.

H3 If you need alternatives

• GitHub hosts open-source Unity asset extractors if you want an offline route.
• Apktool is useful when you want the Android resources decoded locally before touching Unity content.

Next step: upload the APK once and check the output listing before downloading anything — confirm both C# assemblies and asset folders appear, since that tells you whether the game is a standard Unity build or uses custom packing.

What file types can I upload to Decompiler.com for decompilation?

Decompiler.com accepts a broad range of compiled artifacts, grouping them by platform or runtime.

Java and JVM

• .jar, .war, .ear, .class — decompiled back to Java source.

Android

• .apk, .xapk, .aab, .aar, .apkm, .apks, .dex, .smali — decompiled back to Java source, with Unity game asset and C# extraction also mentioned.

.NET

• .exe, .dll — covers C#, F# and Visual Basic, output as a C# project.

Python

• .pyc, .pyo, .rpyc — decompilation, plus .rpa archive extraction.

Lua and Roblox

• .luac, .lub, .luau, LuaJIT — back to Lua source; also .rbxl, .rbxm, .rbxlx, .rbxmx for Roblox extraction.

Games and other binaries

• .swf (Flash, back to .fla and resources), .asar (Electron source browsing), .hbc/.bundle (Hermes), .bsp, .smx/.amxx.

A practical next step: match your file to the right category before uploading, since the output differs — a .dll gives you a C# project, while an .apk gives Java source plus assets. If you only need to inspect one class, extract it first and upload the .class rather than the whole archive; it uploads faster and the result is easier to read. If you are unsure which format you have, check the file extension against the list above, and note that drag-and-drop may fail if an ad blocker is active.

How do I use Decompiler.com to decompile a Python .pyc file?

Upload the .pyc file to Decompiler.com, let it process, then read the recovered source in the browser or download it. The site accepts .pyc, .pyo, .rpyc, and .rpa (Ren'Py archives), so it covers both standard CPython bytecode and Ren'Py game files. Because it runs in the browser, there is nothing to install — useful when you are on a locked-down machine or want a quick look before committing to a local toolchain.

Step by step

1. Open the site and find the upload area (drag-and-drop or "Choose file").
2. Drop in your .pyc file. If drag-and-drop fails, an ad blocker is the usual cause — disable it for this page and reload, or use the file picker instead.
3. Wait for decompilation, then view the result online or download it.
4. Read the output with the version caveat below in mind.

A realistic scenario

You inherit a small internal tool as a compiled .pyc only — the original .py is gone. You want to know what it does before running it. Uploading the file and skimming the recovered source is faster than setting up a local decompiler, and it tells you whether a deeper local analysis is worth the effort.

What to watch for

• Version sensitivity. Python bytecode changes between releases, and decompilers often lag the newest ones. A file built with a very recent Python may fail or decompile imperfectly; older bytecode generally fares better.
• Fidelity. Expect readable logic, but not always byte-for-byte original source — comments, formatting, and some names are lost in compilation and cannot come back.
• Sensitive code. You are uploading the artifact to a third-party service. For proprietary or regulated code, a local decompiler keeps it on your machine.
• Ren'Py specifics. .rpyc files are Ren'Py's compiled scripts; .rpa is its archive format, which the site extracts rather than decompiles. If your goal is game modding, check the site's dedicated Ren'Py and game-asset pages for the right path.

When to prefer a local tool instead

If you need to batch-process many files, work offline, or handle code you cannot upload, a local decompiler is the better fit. Use the online service for one-off inspection and quick answers; switch to a local setup when the job becomes routine or confidential.