ads.txt Generator

How to use

1. 1Pick /ads.txt for a website or /app-ads.txt for mobile apps, then choose a template (Minimal AdSense, Independent publisher, Managed agency, Mobile app, or Blank slate) to load a working file.
2. 2Add the variables you need. CONTACT lets buyers reach you, OWNERDOMAIN declares the root domain that owns the inventory, and MANAGERDOMAIN is for managed inventory with an optional ISO 3166 country suffix like US or GB.
3. 3Add records or click a network preset (AdSense, Ad Manager, OpenX, PubMatic, Magnite, Sovrn, Criteo, Media.net, Amazon, Index Exchange) and replace the placeholder publisher ID with the value your network dashboard shows.
4. 4Pick DIRECT for a direct contract or RESELLER for an authorised reseller. Paste the TAG-ID the seller publishes when the row needs one.
5. 5Watch the live error and warning counts. Click Copy file to grab the UTF-8 text, then host it at https://your-domain/ads.txt or app-ads.txt with Content-Type text/plain; charset=utf-8.
6. 6Switch to the Validator tab to audit an existing file. Each line is classified and any errors or warnings are listed inline with severity colours.

About this tool

ads.txt Generator and Validator builds a standards-compliant ads.txt or app-ads.txt file in two clicks, following the IAB Tech Lab Authorized Digital Sellers (ads.txt) v1.1 spec. Switch the generator to /ads.txt for websites or /app-ads.txt for mobile apps, then pick a starting template (Minimal AdSense, Independent publisher, Managed by an ad agency, Mobile app, or Blank slate) to drop in a working file with one click. The records editor handles the four data fields of every line: exchange domain (validated against a real domain regex), publisher account ID (whitespace rejected), account type (DIRECT or RESELLER, normalised to uppercase), and the optional TAG-ID (also called CERT ID, a 16-character hex string that vendors publish to prove the relationship). Network presets drop in template rows for Google AdSense, Google Ad Manager, Amazon Publisher Services, OpenX, PubMatic, Magnite, Index Exchange, Sovrn, Criteo, and Media.net using the TAG-IDs each network publishes. The variables editor supports all five v1.1 variables: CONTACT for buyer reach-out (validated as either a URL or an email), SUBDOMAIN to delegate a subdomain to its own ads.txt, OWNERDOMAIN to declare the root domain that owns the inventory, MANAGERDOMAIN for managed inventory with an optional ISO 3166 country code, and INVENTORYPARTNERDOMAIN for inventory sharing partners. The output panel shows the exact UTF-8 text the spec requires, including the generated header comment, the variables block, the records block, and any free-form notes you add, with a single Copy file button. The Validator tab parses any ads.txt or app-ads.txt you paste line by line, classifies every line as a record, a variable, a comment, a blank line, or an invalid line, and produces a summary of records, variables, errors, warnings, and duplicate records detected by exchange domain plus publisher ID plus account type plus TAG-ID. Issues are surfaced inline with severity colours so you can fix the file in the same view. Useful for publishers preparing or auditing their ads.txt for AdSense or Ad Manager, ad ops teams reconciling reseller relationships across exchanges, mobile developers shipping app-ads.txt at the developer site listed in their App Store or Play Store page, agencies setting up managed inventory with MANAGERDOMAIN, and anyone who has had a ad-monetisation review return with an ads.txt warning. All parsing, validation, and file building runs in the browser, so publisher IDs, contact addresses, and reseller domains stay on your device.

Free to use. Works in your browser. No signup, no login.