See the declared application structure
Read the root package.json for a name, version, entry point, and dependency declarations. Missing information stays marked as unknown.
REA Workbench / Browser tool
100% local processingASAR inspector.
A clearer view of your Electron app. Open the archive, find a clue,
and bring a better question to Reverse Engineer Anything.
A little curiosity. One ASAR file.
Drop your app.asar here to see what’s inside.
No uploads. No account. Up to 1 GiB.Your files never leave your browserSource displayed, never executedExport findings for your workflow
What’s in an ASAR?An archive.
An archive.
A starting point.
Electron apps often bundle their JavaScript, assets, and package metadata in an app.asar file. This ASAR viewer reads that archive directly in your browser, without installing Electron or REA.
Find useful analysis clues
Source map candidates can point toward original source. Native modules may require a separate analysis provider. Unpacked files need the adjacent folder.
Continue with REA
Download a Markdown summary or copy a focused investigation task. Reverse Engineer Anything can help trace a feature beyond this static overview.
Know the boundaries
This tool inspects ASAR structure; it does not decompile native binaries, run the app, or recover a remote backend. Dependency ranges are declarations, not verified installed versions. Archives up to 1 GiB, headers up to 16 MiB, and up to 100,000 entries are supported. Text previews show the first 256 KiB. Larger archives can be analyzed with the local REA CLI.
Need a file to explore? “Try an example” creates our original Fieldnotes fixture in memory. It contains a small Electron-style CSV export flow for learning.