>IMO there's a reason why YouTube only encodes AV1 for certain videos - I suspect it's based off of a view count. Past that point they trigger a AV1 encode, but it isn't worth it to do all videos, at least right now.
But how can they do that without storing the original uploaded video until it hits that view count?
Do they actually store the original uploaded video somewhere, but reencode for the edge servers to save data/storage?
> Do they actually store the original uploaded video somewhere, but reencode for the edge servers to save data/storage?
YouTube has always stored the original video indefinitely. When they added 60FPS support, videos going back years were suddenly available with 60FPS without having to re-upload them. Not many people bothered to upload in 60FPS before YouTube supported it, but those that did noticed. (I know from Rooster Teeth/Achievement Hunter, which did 60FPS before YouTube supported it possibly because they also had their own platform in parallel.)