Code · Made a little simpler

App-ads.txt Validator

Validate saved app-ads.txt seller syntax and trace candidate file locations from the developer website supplied by an app store listing.

Free to useNo account neededProcessed on your device
Your workspaceProcessed on your device

Add this tool to your website

Paste this code into your page to add the tool and a visible ToolMellow credit link.

HTML embed code
Preview embed

App-ads.txt Validator: how to use it

  1. Paste or open your app-ads.txt. Optionally enter the store-listed developer website and the URL of the file you saved.
  2. Select Validate app-ads.txt. Check account IDs and seller types, then compare the calculated preferred and fallback file locations.
  3. Download the JSON report with the row findings, original source and derived locations.

Limits and notes

Checks local text up to 256,000 UTF-16 units and 10,000 physical lines using ads.txt 1.1 record syntax. Country declarations are checked for two-letter format. The report uses supplied URLs and the bundled Public Suffix List. A deployment check requires separate HTTP, redirect and publisher evidence.

How your privacy works →

App-ads.txt Validator: common questions

Where does the preferred candidate come from?

From the supplied developer website, using the registrable domain and the subdomain label nearest it. The common www and m labels are ignored. The file sits at /app-ads.txt on the resulting host.

When does the parent fallback apply?

The app specification gives the preferred subdomain file priority if one is found. With a distinct preferred subdomain, the parent location is shown as a fallback candidate.

What does INVENTORYPARTNERDOMAIN point to?

It names an inventory partner. Under the shared ads.txt specification the partner document is ads.txt on the named domain.

How do I verify an account ID?

Compare its exact spelling with the advertising system’s published instructions or the identifier supplied for your account. The local check validates field formatting.

Guides