Customizing the visual backdrop during video calls to enhance privacy or presentation
Indeed! At least I have the support call written response to show that Microsoft knows that it is an issue.
John
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Indeed! At least I have the support call written response to show that Microsoft knows that it is an issue.
John
Hi
I was having the same issue. I manually uploaded the custom images to the "Uploads" folder within the Teams cache folder and this enabled me to select the desired custom image in the background settings during a call. I realize this is not a solution for administrators that need to deploy a customized background to many users, but if you are the only affected user, this might help
Regards
SC
I went through the "Clear cache" route. It does work, however there is a mistake on the path provided, at least in my case. It has to end with MSTeams, not just Teams.
Now, let's hope Microsoft will properly fix this.
%userprofile%\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft*MSTeams*
I just went through this with a team member. We were only able to get it to accept images at 800 x 448 and 72ppi in JPG format. Obv the resolution wasn't fabulous but it was better to have the proper image than not. Hopefully this helps some peeps out until Microsoft can figure out the bug :-)
Hi, I am experiencing the same thing