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.
Reverting back to an older version of teams worked for you? I did mention in my reports that it was with the new update.
Unfortunately we can't revert back versions, our corporate way of working is locked down.
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.
Agreed, downgrading to an older version should not be a fix. With our environment and patching regularly with thousands of computers; it doesn't work for us. Microsoft needs to fix the bug.
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
lol.. hopefully it is not like the OneDrive sync issue at the beginning of the year where they said the same thing... then 3 updates later it was still broken! I don't understand why they can't just create a service health issue when they know an issue is occuring! It is impossible to explain these issues to users that insist on seeing official documentation that there is a known issue.