AppImage Extractor Online — Unpack AppImage Files
Extract the files packaged inside a Linux AppImage. Explore application resources and supported embedded code from your browser, without launching the app.
How to extract an AppImage online
- Upload your
.AppImagefile. You do not need to make it executable, install FUSE or use a Linux terminal. - Browse the application folders and inspect supported scripts, images, configuration and other resources.
- Download the files you need or save the completed extraction as a ZIP.
What is inside an AppImage?
An AppImage packages a Linux application and its resources into one file. Supported type-2 AppImages contain a SquashFS filesystem. The extracted application directory can include AppRun, desktop entries, icons, libraries and folders such as usr/bin and usr/share. Contents vary by application.
This extractor reads the packaged files without executing the AppImage runtime or its AppRun entry point. It works through a browser on Windows, macOS and Linux, so no local AppImage extraction command is needed.
Inspect Electron assets and embedded code
If the AppImage contains a supported Electron app.asar, its packaged JavaScript, HTML, CSS and assets are unpacked automatically. Other supported nested archives and Java, .NET, Python or Lua bytecode can also be processed within the same job.
Native Linux executables and libraries remain downloadable files. Their original C or C++ source is not recovered, and extraction does not restore an application's original project or turn a Linux program into a Windows or Mac application.
Supported AppImage formats
This tool supports type-2 AppImages with SquashFS 4.0 compressed using gzip, XZ, LZO or Zstandard. Type-1 AppImages, older SquashFS versions, LZ4 and LZMA compression are unsupported. Unusual runtime layouts or damaged images can also prevent extraction.
Regular files are extracted; symbolic links and special files are skipped with notes. The result is intended for inspecting contents and does not reconstruct a runnable AppImage.
AppImage extraction questions
Can I unpack an AppImage on Windows or Mac?
Yes. Upload a supported AppImage and browse its files online. No Linux installation is required for extraction; running the packaged application is a separate task.
Is this the same as running --appimage-extract?
Both workflows aim to expose the packaged files. Here, the AppImage runtime is never executed: the service reads its filesystem as data and returns supported regular files within the published limits.
Can I download an AppImage as a ZIP?
After extraction finishes, use Download ZIP to save the recovered contents. This is an export of extracted files, not a conversion into another executable format.
Can I inspect several AppImages together?
Put them in a ZIP named apps.filesystem.zip and upload that bundle. All images share one extraction budget. A bundle can also contain supported Mac DMG files.
Why is an AppImage unsupported?
Its type, compression, filesystem version or runtime layout may fall outside the supported formats. Damaged images and extraction limits can also prevent completion. Check the result's notes for the reason.
Extraction limits and partial results
Processing allows up to 1 GiB of expanded data and working copies, 256 MiB per extracted file or DMG partition, 25,000 entries and four nested layers. Filesystem layers count toward that depth. The extraction and code-recovery time limit is five minutes; worker limits can stop processing sooner.
You can browse completed files while extraction continues and download the result as a ZIP when processing finishes. If a limit or unsupported format stops extraction, completed files remain available. Check extraction.json and DECOMPILATION-NOTES.txt for details about missing content.
Where are files processed?
Files are uploaded to our servers for extraction. Disk images are never mounted, and the application inside your upload is never run or installed. Use the result's Delete control to remove its artifacts. Read our privacy policy for data handling.