Export Mobile JSON from Axe Developer Hub

Mobile projects in Axe Developer Hub can export a session as Mobile JSON: a zip archive containing one JSON file per result, with each result's screenshot and view hierarchy attached. This is the same format produced by the Axe DevTools Mobile dashboard, and it's the format Axe DevTools Reporter CLI expects as input.

This export option is available only on mobile projects. Web projects use JSON and CSV export instead.

Which Format Should I Use?

The export modal offers two formats:

• Mobile JSON (selected by default) includes everything captured during the scan: the accessibility results, screenshots, and the full mobile view hierarchy for every result in the session.
• Axe Universal JSON contains only the accessibility results, in the same schema used across Axe products, with no screenshots or view hierarchy.

Choose Mobile JSON when you want to open the results with Reporter CLI, when Deque support asks you for a scan export while troubleshooting, or whenever you need the screenshot or view hierarchy for a result. Choose Axe Universal JSON when you're feeding results into a tool that expects axe-core-style JSON and doesn't use the mobile-specific fields, or when you want a consistent output shape across your web and mobile projects.

For the full comparison, see Which format should I use? in the Axe DevTools Mobile documentation — the in-app help link in the export modal points there as well.

Export a Mobile Session

1. Navigate to a mobile project and open the session (issues list) you want to export.

2. Click Export.

3. In the Format type picker, select Mobile JSON (or leave it selected, since it's the default).

4. Click Export to confirm.

   note

   While the export is processing, the modal shows a blocking progress state and can't be dismissed until the download finishes or fails. If it fails, an error message appears in the same modal with a Try Again option that retries the download with the same format you already selected — you don't need to reopen the format picker.

5. Once the download completes, unzip the file. Extract it to a folder before pointing any tooling (like Reporter CLI) at the results — the zip itself isn't a valid input.

What's in the Download

• The zip is named after the session, for example My-Session_2026-04-27T14-30-15.zip (a generic Scan-Report_<timestamp>.zip name is used if the session has no display name). Any character in the session name that isn't a letter, digit, underscore, dot, or hyphen (including spaces) is replaced with a hyphen; consecutive hyphens collapse into one, and leading or trailing hyphens are trimmed.
• It contains one JSON file per result in the session, each named after that result's internal identifier rather than anything human-readable.
• Each result's file has its screenshot and view hierarchy attached, unless your instance has no screenshots available (see the on-prem note below).
• The export always includes every result in the session — it does not honor any filters (such as selected screens) currently applied to the issues list.

Using the Export

With Reporter CLI: extract the zip to a directory, then run Reporter CLI against that directory to generate a report:

./reporter-cli-<your-system> <extracted-results-directory> <output-directory> --format=html

See Use Reporter CLI with Automated Testing for the full command reference and other output formats.

With Deque support: if a support engineer asks you for a scan export while troubleshooting an issue, send them the Mobile JSON zip — it's the format their tools expect.

Who Can Export

Anyone who can already view and export results for a mobile project can export Mobile JSON — no additional permission or license is required.

Troubleshooting

• The format picker offers JSON/CSV instead of Mobile JSON/Axe Universal JSON: you're on a web project. Mobile JSON export only appears on mobile project pages.
• Export fails or times out on a very large session: the export is capped at 30 seconds. If the zip isn't ready by then, the request is aborted and the export fails. Larger sessions are more likely to hit this limit. If it consistently fails, try again later or contact Deque support.

What's Next?

Return to Understand Your Results to learn about filtering, comparisons, and the rest of the issues list, or see Axe DevTools Reporter CLI for generating shareable reports from your export.