This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
We are trying to upload 1920 x 1080 custom backgrounds and we are getting an error message saying invalid size. Testing other sizes, anything square 1:1 works but gets cropped in the viewer. We also tried 1280 x 800, but same gets cropped. There isn't mention of this update in any of the update logs. What is the correct size, is there a template to follow to know what gets cropped?
Customizing the visual backdrop during video calls to enhance privacy or presentation
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
We have this same error
Work around is to change the background size
This will allow you to upload the image
Our company is having the same problem. Users reported it this morning. Two helpdesk people tried it and got the same results, even with images that have been used before.
I have not received an official MS solution to this issue as if yet, March 20, 2025.
We are still receiving the error when trying to upload 1920 x 1080. For a temporary fix, our team is exporting images out in the 1200 pixel size (1200 x 675, 1280 x 720). The viewing window is in 16:9 ratio and these smaller sizes are uploading without issue.
To confirm I converted an image to 1280 x 720 and increased the file size to 1.5 MBs and it uploaded fine. The same image at 1920 x 1080 at 180 kbs failed to upload. This has nothing to do with the file size and is 100% a bug on image sizes.
I talked with Microsoft support today, and they are aware of the issue, which was caused by their latest update. They haven't bothered to show it in M365 as a current issue, but they said that it will be fixed in the next Teams update. No timeframe on that.
John