ARSC Decompiler and Viewer Online

What Is a resources.arsc File?

resources.arsc is the compiled Android resource table commonly found inside an APK file. It maps resource IDs to names, types and values, including strings, colors, dimensions and references to files such as layouts and images. It also records variants for different device configurations, such as language, screen density and night mode.

The table is binary, so opening it in a text editor does not show its structure clearly. This online ARSC file viewer decodes the table into readable JSON that you can browse and download without installing a desktop tool.

What You Can View and Extract

• Packages and resource IDs: package names and IDs, resource names, types and numeric IDs.
• Values: strings, colors, booleans, integers and dimensions, with their encoded type and raw data.
• Configuration variants: default values and available locale, density, orientation, night mode and Android API qualifiers.
• Arrays, plurals and styles: ordered items, plural quantities and style parent references.
• References: resource IDs and file paths stored in the table. Reference chains are preserved without being followed.

The output starts with summary.json, followed by JSON files under packages/, grouped by package, configuration and resource type. When decoding is incomplete, the summary and DECOMPILATION-NOTES.txt explain the limitations.

Try a Sample resources.arsc File

Download the sample resources.arsc and upload it above. This small, original example contains two packages, strings, a color, an array, plurals, a style and configuration variants. It contains no data from a real application.

For example, its default greeting string appears as this resource entry in the decoded JSON:

{
  "id": "0x7f010000",
  "name": "greeting",
  "type": "string",
  "value": {
    "dataType": 3,
    "rawData": "0x00000000",
    "text": "Hello <world> & friends"
  }
}

Does an ARSC File Extractor Recover Images and Layouts?

A standalone ARSC file contains table values and references, including paths such as res/layout/main.xml. The referenced image and layout files are separate entries in the APK and cannot be reconstructed from the table alone. Upload the complete app to the APK decompiler to inspect those files alongside the resource table and code. For split app packages, use the XAPK decompiler.

Standalone ARSC decoding produces JSON, rather than an original Android project or XML resource export. Styled string text is preserved, but formatting spans are not reconstructed. Some advanced table features, including dynamic library mappings, overlays and staged aliases, are not applied; affected output is marked as partial.

Frequently Asked Questions