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
Read ASAR archives locally in your browser and export their packaged files.
Choose filesDrop a file here, or click to choose
.asar
Max 5 MB
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Open an Electron .asar archive to browse its directory index and export safely readable packaged files as a ZIP.
ASAR contains indexed file data, while native modules, large files, links, or other external entries may remain in a sibling app.asar.unpacked directory.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Select an authorized .asar file no larger than 5 MB.
Start processing so the browser can read the archive header and index, then validate entry paths, offsets, sizes, and boundaries.
Filter entries by archive path and preview supported text files; long previews show only their beginning.
Download the ZIP for complete extracted bytes, including binary files and text formats unavailable in the preview.
Tip: If external entries are reported, retrieve them from the original installation while preserving their relative locations.
Use cases
See how the tool fits into real work and everyday tasks.
Check configuration, interface text, and resources in your development or test build.
Inspect scripts and resource paths for missing files, version differences, or loading errors.
Review an authorized archive without running the packaged application.
Q&A
Find concise answers to common questions and confusing cases.
They may be stored outside the archive in app.asar.unpacked and cannot be recovered from the ASAR alone.
An entry with an unsafe path or invalid file boundary may be skipped, or the archive may fail to process.
Not necessarily; rebuilding may require external files, links, permissions, dependencies, the original directory structure, packaging configuration, and signing process.
Notes
Review scope, result limitations, and important precautions before use.
Only inspect archives you own or are authorized to process; extraction does not grant rights to modify, distribute, or bypass access controls.
Processing occurs in your current browser and the archive is not sent to a decompilation server, but extracted files may expose tokens, endpoints, accounts, internal scripts, or business logic, so protect the downloaded ZIP.
Browser memory, directory depth, entry count, and total extracted-size limits can produce incomplete results, while minification, obfuscation, or generated files may reduce readability.
Related
Discover related tools, collections, and available API capabilities.