2026-10-04

Why your Zoom, Teams, or Google Meet background looks blurry or stretched — the exact size each one actually wants

Search any video-call platform's name next to the word “background” and you'll find years of the same complaint: the picture looks fine as a photo, but the moment it's applied as a virtual background it comes out soft, pixelated, or stretched sideways. Microsoft's own community forum has multiple open threads on it — one titled simply “Custom Teams background upload is blurry”, another “Custom Background Pixelation” — and Zoom's own user community has the same thread under a different name, “Uploaded Virtual Background Poor and Pixelated Quality.” The three platforms turn out to document wildly different numbers — and in one very common case, no number at all.

Zoom publishes an exact spec — for every user

Zoom's own support documentation is the most specific of the three. It states that a virtual background image must be in “24-bit PNG or JPG/JPEG image format” with a “maximum image size” of 15MB. On resolution, it recommends “cropping the image to match the aspect ratio of your camera” — for a typical 16:9 camera, it gives 1280×720 or 1920×1080 as examples that work well, and if you don't know your camera's aspect ratio, it says to use a minimum of 1280×720. This is published on the same support page every regular Zoom user reaches when changing their own background — not a separate admin-only document.

Microsoft Teams: admins get an exact range, everyone else gets a file-format list

Microsoft splits this in two, and the split explains a lot of those forum threads. The consumer-facing support article, “Change your background in Microsoft Teams meetings” — the page an ordinary user reaches to upload their own photo — states only that the file needs to be “a .JPG, .PNG, or .BMP file.” No resolution, aspect ratio, or file-size number appears on that page at all.

A second, separate Microsoft Learn article aimed at IT admins — for uploading a shared background library that Teams Premium users can select from — is far more precise. It states images must have “a minimum dimension of 360 px X 360 px” and “a maximum dimension of 3840 px X 2160 px,” accepts only “PNG and JPEG” formats, and caps the library at “a maximum of 50 custom background images.” It also notes that the “frosted glass” effect specifically requires uploading a transparent PNG — the clear part of the file becomes the blurred glass area. An everyday Teams user picking their own photo never sees any of these numbers; they're only written down for the admin console.

Google Meet: the same gap, mirrored

Google Workspace's admin documentation for organization-wide Meet backgrounds is just as specific as Microsoft's admin page: uploaded images must be in “JPEG format”, “landscape orientation,” with a “maximum size of 1920x1080p,” and an admin can provide “up to 15 custom images for each organizational unit or group.” Meet's own help page for an individual user adding their personal background, by contrast, describes the feature but — like Teams' consumer page — states no file format, resolution, or size requirement at all.

The numbers side by side

One size that clears every bar

A 1920×1080 image in 16:9 lands inside Zoom's recommended range, sits comfortably within Teams' admin-documented 360×360–3840×2160 window, and matches Google's admin cap of 1920×1080 exactly. It's also a safe bet for the two consumer pages that publish no number at all — matching a published spec elsewhere is a reasonable floor when a platform's own page for your account type doesn't give you one.

Building it with nearIMG

• Crop to 16:9 first. All three platforms assume a landscape, camera-shaped frame; a square product photo or a tall phone screenshot used as-is is exactly what gets stretched or cropped unpredictably when the call software forces it into that shape.
• Resize to 1920×1080. This is the one number that sits inside every range above instead of just one of them, and it avoids the soft, upscaled look that several of the forum threads describe — which typically happens when a smaller source gets stretched up rather than captured or exported at full size.
• Convert to PNG or JPG — both are accepted everywhere in the table above; only Google Meet's admin spec narrows that to JPEG specifically.
• Compress if the exported file is still above Zoom's 15MB ceiling, which can happen with an unedited photo straight off a modern phone camera.
• Because nearIMG runs entirely in the browser, this applies to a company logo or an office photo you'd rather not upload to a random online converter just to resize it.

What this doesn't do

• It doesn't remove or replace a background in real time. The actual person/background segmentation during a live call is each platform's own camera-feed feature; nearIMG prepares the static image file you hand to that feature, it doesn't run during the call.
• It doesn't cut a subject out to transparency. Teams' frosted-glass effect needs a transparent PNG with the subject already isolated; nearIMG's Crop and Convert tools don't perform background removal.
• It doesn't guarantee Teams or Google Meet will accept a given file for their consumer upload flow, since those specific pages don't publish a resolution requirement to test against in the first place — 1920×1080 is the best-documented common denominator, not a number either page promises will work.

The short version

Zoom's own support page gives every user an exact spec: 24-bit PNG or JPG, under 15MB, matching the camera's aspect ratio at roughly 1280×720 to 1920×1080 for a 16:9 frame. Microsoft Teams and Google Meet only publish that level of detail for their admin-managed background libraries — 360×360 up to 3840×2160 for Teams, a flat 1920×1080 cap for Google Meet — while the page an everyday user reaches to upload their own photo says little more than which file formats it accepts, or nothing at all. Cropping to 16:9, resizing to 1920×1080, and converting to PNG or JPG with nearIMG covers every published range at once.