ASAR Viewer
Look inside a desktop app's .asar archive that you own or have the right to inspect: its files, what takes the space, its code and the web addresses in it. Free, with no sign up. Your file stays in this browser; nothing is uploaded.
Files
| Name | Size | Where |
|---|
Selected
Web addresses in the code
Where .asar files live
A desktop app built with Electron keeps its code in an archive named app.asar inside its resources folder.
Windows: the app's install folder, then resources. Mac: Show Package Contents, then Contents/Resources. Linux: often /opt/<app>/resources.
What an app's archive can tell you
- Which servers an app talks to, before you allow it through a firewall.
- What takes the space in a large download: code, images or bundled libraries.
- Which native add-ons and programs it keeps outside the archive.
- Whether a file was changed after the archive was made, when hashes are recorded.
Open only files you own or have the right to inspect. This page reads the archive only; it does not run, change or unlock anything.
How to use this tool
Pick an .asar file you own or have the right to inspect, or try the sample. Hover the size map to see what takes the space, click a file to read it, and check the web addresses the app's code holds.
Frequently asked questions
Is my file uploaded?
No. The page reads the archive's index first, then only the file you click, each by its own place in the archive. Nothing leaves your browser and the page makes no network call with it.
What is an .asar file?
A simple archive that desktop apps built with Electron use to hold their code: a small header, a JSON index of every file with its size and place, then the files' bytes one after another. It is not compressed or encrypted.
Where do I find app.asar?
In the app's resources folder. On Windows look in the app's install folder under resources. On a Mac, right-click the app, choose Show Package Contents, then open Contents/Resources. On Linux it is often under /opt/<app>/resources.
Why are some files marked outside?
An app can keep some files out of the archive, usually native add-ons and programs that must run from disk. The index still lists them, but their bytes live in a folder named app.asar.unpacked next to the archive. Open that folder to read them.
How are the web addresses found?
The page reads every text file in the archive (code, JSON, HTML, CSS) and lists anything that starts with http, https, ws or ftp, grouped by host, with the files it came from. It also lists quoted text shaped like a server name. Addresses that are built while the app runs can be missed.
What does Check hash do?
Newer archives record a SHA-256 hash for each file. Check hash works out the hash of the file's bytes in your browser and says whether it matches the index. A mismatch means the file was changed after the archive was made.