OpenRTB specification versions
IAB Tech Lab publishes OpenRTB. Versions 2.0 to 2.5 are PDFs linked from the IAB Tech Lab OpenRTB page, the current 2.6 line lives in the openrtb2.x repository as dated snapshots, and 3.0 lives in the openrtb repository. The table below links each version to its official text and to a page describing what it changed.
Every version
Each version page lists the fields that release added, deprecated, or removed, and every object it defines. To compare two versions directly, use the version diff tool.
Which version to target
New integrations should target the latest 2.6 snapshot. OpenRTB 2.5 (December 2016) is still common in older SDKs and exchange contracts, and 2.6 is backward compatible with it apart from a handful of removed fields. OpenRTB 3.0 is a separate design with little adoption. The 2.5 versus 2.6 guide and the 2.6 versus 3.0 guide cover the migrations.
Why the 2.6 line has dated snapshots
OpenRTB 2.6 is not a single frozen document. Since April 2022 IAB Tech Lab has shipped revisions that add, deprecate, and move fields without changing the version string, so calling a payload OpenRTB 2.6 is not precise enough. Between snapshots the GDPR signal moved out of an ext block, plcmt replaced placement for video, and duration floors arrived. Validate against the wrong revision and you either miss a moved field or flag one that is correct for your partner.
2.6-202204(2022-04)2.6-202210(2022-10)2.6-202211(2022-11)2.6-202303(2023-04)2.6-202309(2023-09)2.6-202402(2024-02)2.6-202409(2024-09)2.6-202501(2025-01)2.6-202505(2025-05)2.6-202606(2026-06)
The tester defaults to the latest snapshot and can pin any earlier one, as can the CLI with rtblint validate --version 2.6-202303.
Where IAB Tech Lab publishes OpenRTB and related specs
| Repository | What it holds |
|---|---|
| openrtb2.x | OpenRTB 2.6 in Markdown (2.6.md), each dated snapshot as a tagged release, and the implementation guide. |
| openrtb | OpenRTB 3.0, the ads.cert signed bid request draft, the original SupplyChain object document, and community extensions. |
| AdCOM | The enumerated lists OpenRTB 2.6 points to (device types, plcmt, API frameworks, and the rest) and the object model OpenRTB 3.0 uses. |
| Native-Ads | The Native Ads request and response specification carried inside imp.native.request and the native adm. |
| Global-Privacy-Platform | The GPP string carried in regs.gpp, with every section layout referenced by regs.gpp_sid. |
| GDPR-Transparency-and-Consent-Framework | The TCF consent string carried in user.consent, maintained with IAB Europe. |
| VAST | The video ad markup a video bid returns in adm or by reference. |
ads.txt, app-ads.txt, and sellers.json are published on the IAB Tech Lab ads.txt page and the sellers.json page.
What RTBlint covers per version
RTBlint ships object catalogs for 17 of the 18 documented versions, 2.0 through 3.0, so undefined-field and type checks work across the whole line, and each version carries a profile describing what that release changed. The April 2022 archive has no extractable object catalog; validation for it uses the 2.6-202210 republication. Rule depth (deprecations, moves, and semantic checks) is richest on the 2.6 snapshots. OpenRTB 3.0 validates through its openrtb envelope, including the AdCOM objects under item.spec, bid.media, and request.context. Each supported version also has a JSON Schema generated from the same catalogs.