Playback support is not editing support
AV1 and VP9 are common delivery codecs on the web. Browsers and media players may decode them even when an editing application does not provide the same native import path. That is why “it plays in Chrome” is not a compatibility test for Premiere.
AV1 remains a moving target in Premiere
Adobe’s 2026 feature-request forum still shows native AV1 encoding and decoding as an active request, and an Adobe Community Manager stated in February 2026 that the team was considering it without further information to share.
Because this can change in a future Premiere release, ClipCompat keeps AV1 guidance date-sensitive and uses Test Required rather than turning old forum knowledge into a permanent rule.
Third-party importers change the environment
Third-party plug-ins may add AV1, VP9, WebM or MKV import paths, but that means compatibility is now tied to that plug-in’s supported Premiere versions, operating systems and hardware. A file that works through a plug-in should not be described as universally supported by Premiere itself.