app-ads.txt Generator and Validator

๐Ÿ“„

app-ads.txt Generator & Validator

Create a correct app-ads.txt file for AdMob, Meta Audience Network, Unity Ads, AppLovin and other ad networks, or paste an existing file to find the errors that cause "app-ads.txt not found" or "not verified" warnings.

Your publisher ID from AdMob > Settings. Use the pub- ID, not an App ID (ca-app-pub-...~...).
One ID per line is created. Separate several IDs with commas.
Unity and AppLovin generate a full, account-specific list in their dashboards. Paste it here and the tool will clean it, remove duplicates and merge it with your other lines.

What Is app-ads.txt?

app-ads.txt (short for Authorized Sellers for Apps) is a plain text file that tells advertisers which companies are allowed to sell ad space inside your mobile apps and games. It was created by the IAB Tech Lab as the app version of ads.txt for websites. Each line names an ad network, your account ID on that network and the type of relationship you have with it. Ad buyers download this file from your developer website and compare it with the ad requests they receive. If a request comes from a seller that is not listed, many buyers simply refuse to bid.

For indie developers this matters in a very practical way. When AdMob cannot find or verify your app-ads.txt file, you will see warnings in the dashboard and your fill rate and eCPM can drop because a share of demand will not buy unverified inventory. The free app-ads.txt generator above creates a correctly formatted file in seconds, and the validator checks an existing file for the small mistakes that break verification.

How to Use the app-ads.txt Generator

  1. Enter your AdMob publisher ID. Open AdMob, go to Settings and copy the ID that starts with pub- followed by 16 digits. Do not use an App ID or an ad unit ID. Those start with ca-app-pub- and contain a tilde or slash.
  2. Add other networks. If you use Meta Audience Network, enter your Property ID or Business ID. For Unity Ads, AppLovin, ironSource and other mediation partners, copy the full app-ads.txt list from each dashboard and paste it into the extra lines box.
  3. Enter your developer website. Use the exact domain shown on your Google Play or App Store listing. The tool tells you the URL where the file must be uploaded.
  4. Generate, then download. Click Generate, check the result, download app-ads.txt and upload it to the root folder of your website.
  5. Validate. Click "Check it in the validator" to confirm every line passes before you upload.

The app-ads.txt Line Format

Every record is one line with up to four comma-separated fields:

google.com, pub-1234567890123456, DIRECT, f08c47fec0942fa0
  • Ad system domain: the domain of the ad network, for example google.com, facebook.com or unity.com.
  • Publisher account ID: your ID inside that network. For AdMob this is your pub- ID.
  • Relationship: DIRECT if you control the account yourself, or RESELLER if another company sells your inventory for you. AdMob lines use DIRECT. Meta asks for RESELLER.
  • Certification authority ID (optional): a TAG ID that identifies the ad system. Google's is f08c47fec0942fa0 and Meta's is c3e20eee3f780d68.

Lines that start with # are comments. The file can also contain variables such as OWNERDOMAIN=mystudio.com or CONTACT=support@mystudio.com. Unity documents the owner domain variable in its app-ads.txt guide, so it is worth adding if you use Unity Ads.

Where to Upload app-ads.txt

The file must live in the root of the domain listed as your developer website in the store, for example https://mystudio.com/app-ads.txt. A file inside a folder, such as /files/app-ads.txt, will not be found. According to Google's AdMob help, the crawler tries HTTPS first and then HTTP, ignores the www. and m. prefixes when it picks the hostname, and follows redirects.

  • WordPress or cPanel hosting: upload the file to public_html with the File Manager or FTP.
  • No website yet: create a simple one-page site on a domain you own, or use Firebase Hosting, which Google suggests as an option. Free page builders that do not allow root files will not work.
  • Store listing: add the same website URL to the Developer contact section in Google Play Console and to the Marketing or Support URL in App Store Connect.

After upload, open the URL in a private browser window. You should see plain text, not an HTML page, a download prompt or a 404 error.

How Long Does Verification Take?

Google says crawling and verification can take up to 24 hours, and changes to your Google Play listing can also take up to a day to be detected. In AdMob, open Apps, choose View all apps, select the app-ads.txt tab and use "Check for updates" to request a new crawl once the file is live. Meta recommends waiting 24 hours after updating the file before you run its authentication again.

Common app-ads.txt Errors and How to Fix Them

"app-ads.txt not found"

The crawler could not reach the file. Check that the developer website in your store listing is correct, that the file sits in the root folder, that the name is exactly app-ads.txt in lowercase and that your server does not block bots with a firewall or a security plugin.

"Your publisher ID isn't included"

The file was found but your AdMob line is missing or wrong. The most common causes are using the ca-app-pub- App ID instead of the pub- ID, a typo in the 16 digits, or adding a space inside the ID.

Formatting mistakes

  • Curly quotes, tabs or invisible characters copied from a word processor. Always edit the file in a plain text editor.
  • Semicolons instead of commas between fields.
  • Misspelled relationships such as DIRCT or Direct-Reseller.
  • Saving the file as app-ads.txt.txt or as an HTML page.
  • Duplicate lines from copying the same network list twice. Duplicates are not fatal, but they make the file harder to maintain.

Ads limit or low fill after launch

An unverified file is only one reason for an AdMob ad serving limit. Invalid traffic, clicking your own ads and new accounts can also trigger limits. Fix app-ads.txt first because it is the easiest problem to solve, then review the rest of your setup in our guides.

app-ads.txt Checklist Before You Publish

  • Your AdMob line uses your pub- ID, DIRECT and the TAG ID f08c47fec0942fa0.
  • Every mediation partner you use has its lines in the file, copied from its own dashboard.
  • The file is at the root of the exact domain listed in Google Play and the App Store.
  • The URL opens as plain text over HTTPS without errors.
  • You requested a new crawl in AdMob and waited at least 24 hours.
  • You update the file every time you add or remove an ad network.

Frequently Asked Questions

Is app-ads.txt required?

It is not technically required to show ads, but AdMob strongly recommends it, many buyers avoid unverified inventory and Unity says it is required for its banner ads. In practice every monetized app should have one.

Do I need a separate file for each app?

No. One file on your developer website covers every app that lists that website. If you publish apps under different developer websites, each domain needs its own file.

Can I use a subdomain?

The file must be at the root of the host listed in your store listing. Use the same domain in the store and on your server, and do not rely on a subfolder.

Does this tool store my publisher ID?

No. The generator and validator run entirely in your browser. Nothing is sent to our servers.

Building a new game? Name it with our Game Name Generator, write the store listing with the Game Description Generator, check keywords with the ASO Keyword Checker and create a policy with the Privacy Policy Generator.

Ready to publish a new game?

Get a ready-to-publish Unity or Buildbox project with AdMob already integrated, set up app-ads.txt with this tool and start earning faster.

Browse Source Codes

About the Author

AA
Abdullah Akasha
Project Manager, QA Lead & Editor at App Source Market

Abdullah is a computer science graduate who works with development teams to plan, test and ship websites and mobile projects. At App Source Market he builds the free developer tools and writes practical guides that help indie developers name, reskin, monetize and publish Unity and Buildbox games.

Our Research & Testing Process

We build and test every tool with real use in mind. Before publishing, we run it with common and edge-case inputs, check the output against the official AdMob, Meta Audience Network and Unity Ads documentation, and review it for clarity and accuracy. Tools run entirely in your browser, and we revisit them when ad network rules change.

Published: November 22, 2026Last Updated: November 22, 2026Meet Our Team โ†’
Copied!

We use cookies to personalize your experience. By continuing to visit this website you agree to our use of cookies

More