Google Drive's official video format list does not name WebM on its own — it names WebM with two specific codecs inside it. The entry reads "WebM files (Vp8 video codec; Vorbis Audio codec)". If the codecs inside your .webm are something else, your file is not described by that line at all.
That gap is the whole problem. The file uploaded, it sits in your Drive, the thumbnail may even look right — and the player still refuses. Storing and playing are two different systems in Drive, and only one of them accepts anything.
Drive stores everything; Drive plays a short list
Google says this outright on its "Files you can store in Google Drive" page: "Any file type can be stored in Drive. These are the most common file types you can preview in Google Drive:". The sentence introduces a preview list, not a storage rule — storage has already been granted to everything.
So a successful upload tells you nothing about playback. The same page also warns that what you see in the viewer is not the file itself: "The Google Drive preview is a scaled-down version of the complete file and may, when opened, appear slightly different."
Two official pages list video types, and they are not written the same way. The general storage page lists containers only — "Video files (WebM, .MPEG4, .3GPP, .MOV, .AVI, .MPEGPS, .WMV, .FLV, .ogg)". The page dedicated to video, "Store & play video in Google Drive", lists containers with codecs:
WebM files (Vp8 video codec; Vorbis Audio codec)
MPEG4, 3GPP, and MOV files (h264 and MPEG4 video codecs; AAC audio codec)
AVI (MJPEG video codec; PCM audio)
MPEGPS (MPEG2 video codec; MP2 audio)
WMV
FLV (Adobe - FLV1 video codec, MP3 audio)
MTS
OGGIf you only ever read the first page, "WebM is supported" looks settled. Read the video page and the claim gets narrower: supported with VP8 video and Vorbis audio. Google prefaces that list with a caveat worth keeping attached to it: "Not all video types may work on all devices."
"Not listed" is not the same as "not supported"
Be precise here, because the internet is not. WebM is a container. The official entry names one video codec and one audio codec that can live inside it. Other codecs exist that can also live inside a .webm file — VP9 and Opus among them — and Google's pages do not name those anywhere.
What that means, exactly:
- Google has listed WebM with VP8 and Vorbis.
- Google has not listed VP9, Opus, HEVC/H.265 or AV1 anywhere in its video format documentation.
- Google has not stated that those codecs fail. There is no official sentence rejecting them.
So the honest diagnosis is: if your WebM contains codecs other than VP8 and Vorbis, you are outside what Google documents. That is not proof it will fail — but it does mean no official page promises it will work, and it makes an undocumented codec the first thing to rule out. The practical move is to stop debugging the container and check what is actually inside the file.
The fastest fix: move it into a container Drive documents with codecs
The MP4 line is the most specific one on Google's list: "MPEG4, 3GPP, and MOV files (h264 and MPEG4 video codecs; AAC audio codec)". Converting to H.264 video with AAC audio in an MP4 puts your file squarely inside a documented combination instead of an undocumented one.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs in your browser tab — the file is read from disk, re-encoded locally and handed back. Nothing is uploaded to a conversion server, which matters when the video is already sitting in a private Drive folder. Re-upload the MP4 and delete the WebM if the copy plays.
Google's own upload troubleshooting includes the same idea, in its words: "Check the file format: Different video formats are supported by Google Drive, if yours is unusual, you need to convert it." For other containers, MOV to MP4 does the equivalent job, and the full set is at all Clapr tools.
Other causes, in order of likelihood
Before you blame the codec, rule these out — all of them are Google's own documented behaviour.
Third-party cookies are off. Drive's video page states a hard prerequisite: "To play videos in Drive, you need to turn on third-party cookies. Learn how to turn cookies on and off." This one is easy to miss because nothing in the error text mentions cookies. Note that the same page also suggests incognito mode for upload problems, which typically blocks third-party cookies more aggressively — the two tips exist side by side and address different stages.
It is still processing. Google documents an error for this: "Video is still processing. Try again later." — described as "The video is not ready to be played. If the file is large, it may take awhile before your video is ready." How long is not stated anywhere official.
It plays for you and not for anyone else. That is documented rather than mysterious. Drive offers instant playback: "When you upload videos, you can watch them right away", but "This feature is available for videos you upload in the same browser session", and "While you enjoy instant playback, the video might still be processing so that it can be viewed on other devices or by people you shared it with."
The viewer is not signed in. One of Drive's four documented playback errors is "Playback limits": "You've hit the limit for viewers who aren't signed in. To continue to play the video, sign in to your Google Account." Google does not publish the threshold, so do not trust any number you find for it.
The file is broken or in a format that will not work. The bluntest error: "Video is unplayable." Google's stated cause is that "The video may be corrupted or uploaded in a format that won't work. Try to upload the video again or in a different format."
Nothing is wrong except the resolution you expected. Drive's video page sets a playback ceiling: "You can upload video of any resolution, but the minimum size for playback in Drive is 4 KB. The maximum playback resolution is 1920 x 1080." That is a limit on playback, not a statement that your file gets altered — Google never says the stored file is changed. Uploading a 4K master to be watched inside Drive buys you nothing on the playback side.
How to tell it worked
Open the converted MP4 in Drive in a normal (non-incognito) window with third-party cookies allowed, and wait out any "still processing" message. Then check it from a second account or a different device — because of instant playback, your own browser session is the one place that can look fine while everyone else is still waiting.
If it plays for you but a collaborator reports they cannot download it, that is a permissions question rather than a format one. Drive lets owners "prevent" "Viewers and commenters from downloading, printing, or copying files."
FAQ
Does Google Drive support WebM? Google's video help page lists "WebM files (Vp8 video codec; Vorbis Audio codec)". The listing is tied to those two codecs. WebM files built with other codecs are not described on that page in either direction — not listed as working, not declared unsupported.
Is VP9 or Opus supported in Google Drive? Google's documentation does not name VP9 or Opus at all. There is no official statement that they work and none that they fail, so treat it as undocumented and check the official documentation before relying on it.
Why did my WebM upload fine but not play? Because storage and playback are separate. Google states that "Any file type can be stored in Drive" and then gives a much shorter list of what you can preview. A completed upload only proves the first part.
Will Drive compress or re-encode my video? Google's pages do not say. The only number published is a playback ceiling — "The maximum playback resolution is 1920 x 1080" — which describes the player, not your stored file. Claims in either direction about Drive re-encoding your original have no official source.
What should I convert my WebM to? MP4 with H.264 video and AAC audio, which matches the codecs Google names for MPEG4, 3GPP and MOV files. Use WebM to MP4 for that in one pass.
All limits and error text quoted from Google Drive Help — "Store & play video in Google Drive" and "Files you can store in Google Drive" — checked 16 September 2026. Google changes these pages without notice; verify against the official documentation before relying on them. More playback troubleshooting in the fix guides, including Slack WebM video not playing.
