VAST-3.0-bitrate-conflict
VAST-3.0-bitrate-conflict
<MediaFile> has both bitrate and minBitrate/maxBitrate
WarningValuesIAB VAST 3.0 §2.4.1VAST 3.0, 4.0, 4.1, 4.2, and 4.3
Short answer
Providing both bitrate (a fixed value) and minBitrate/maxBitrate (a range) on the same <MediaFile> is contradictory. Use one or the other.
Why this matters in production
This rule is a strong risk signal. Tags with this issue often still parse, but they become brittle across SDKs, SSAI resolvers, and CTV environments. Value-format rules tend to fail at the moment a player interprets a field such as duration, skipoffset, bitrate, or versioning. They are especially painful because the XML can look valid at a glance. Affected scope: VAST 3.0, 4.0, 4.1, 4.2, and 4.3.
How to fix
Remove either bitrate (fixed value) or the minBitrate/maxBitrate pair from <MediaFile> — they are mutually exclusive.
Check your VAST tag for
VAST-3.0-bitrate-conflict and other issues instantly.Open the VAST tag validator →Other Values rules
VAST-4.1-expires-integer<Expires> value must be an integer number of secondsVAST-4.0-category-authority-not-uri<Category> authority attribute is not a valid authority URLVAST-4.0-category-authority-unknown<Category> authority is not a recognised IAB Content Taxonomy authorityVAST-4.1-blockedadcategories-authority-not-uri<BlockedAdCategories> authority attribute is not a valid authority URLVAST-4.1-blockedadcategories-authority-unknown<BlockedAdCategories> authority is not a recognised IAB Content Taxonomy authorityVAST-4.1-verification-vendor-format<Verification> vendor should use a domain-qualified identifier such as company.com-omidVAST-4.1-verification-tracking-reasonverificationNotExecuted tracking URI should include the [REASON] macroVAST-2.0-duration-format<Duration> value does not match HH:MM:SS[.mmm] format