Fix pasting of images
Pasting images is somewhat supported - see https://microsoftteams.uservoice.com/forums/555103-public-preview/suggestions/16925587-ability-to-paste-images) but is not correctly implemented (at least on Windows).
Using Google Chrome, if I right click on any image on a webpage and select "Copy Image", I can not paste it into Teams. I can paste this on competitors products, such as HipChat and of course into MS Paint.
There are different issues pasting from other browsers. Edge and IE both paste a blank image. Firefox has similar behavior to Chrome (nothing is pasted at all).
This is a very common use case - pasting an image from a web page. Please make it work!
Ryan Hoffman
shared this idea
You should experience significant improvements in copy & paste of images within Teams, as well as to & from Teams. We are aware of a few remaining issues, but the most common cases are resolved.
Thanks again for your patience on this one.
177 comments
-
RedJ
commented
This is absolutely NOT fixed. It is still not possible to copy images from the desktop version of Teams to another app.
Open a chat with an image in the stream, click the image to enlarge to full size, right click and select "Copy Image" - the image will be blank in the clipboard manager and is not pasteable to other apps (either blank or not pasteable). I suspect it is not being placed in the clipboard with the correct clipboard format.
I have tried pasting from Teams to Photoshop, Word, and a new Outlook message and none work.
-
Philip Dickason
commented
Not being able to copy an image out of teams into Word/Outlook etc is so frustrating, especially when it gives you the option to "Copy Image" !!
-
Yonah
commented
Good to know you are working on it!
-
Don V Nielsen
commented
@christophe Workaround that I employ is to use a clip tool like Greenshot or DuckLink. Click the image to see it full size and use the other tools. It's a kludge. It works.
-
christophe
commented
Same issue here, someone found a better workaround then download the image before you can use it in a mail?
-
John Slack
commented
Odd for this fix to take so long, isn't it?
-
Levi
commented
Seriously, two years later and we still can't copy/paste an image from Chrome into Teams?
Get it together - how this isn't the highest priority item is beyond me.
Sick of coworkers complaining to me about it. -
Josh Lloyd
commented
I am constantly annoyed by this. I regularly use a workaround of Win+shift+S to screen clip in order to paste in to teams.
-
Matthieu T
commented
Almost 2 years and no update for such a small yet important feature!
It's really odd to offer "Copy image", but working only inside Teams.Please Microsoft, fix this.
Thanks -
Roger Schmidt
commented
Any news? I will postpone upgrade from SfB to Teams (MS is currently pushing it) as this is not the only issue for me (especially due to missing features like sharing desktop directly from chat when collaborating with external partners).
-
Eric Miller
commented
still an issue (5/30/19)
-
Michael W
commented
Any update?
-
Alex Gilbert
commented
2017: We've fixed this bug!
Also 2017: Guess we didn't fix it, but we will soon!Everyone in 2019: *sigh*
-
Dave Boltman
commented
Still an issue as of today (Teams.exe v1.2.0.8864, Windows 10 64-bit v1803, build 17134.706)
-
Sebastian
commented
I really don't understand what is the purpose behind that behavior.
-
Hussein Salamey
commented
Any update here?
-
Dylan
commented
@alex Please advise on an update on this issue, still happening intermittently for all users!
-
Scott Davies
commented
Is this still an issue and being worked on 2 years later or is this fixed now?!
-
Daniel
commented
Seriously, coming from Slack, where pressing Ctrl+V will immediately upload an image, the Teams exprience is horrible. Pressing Ctrl+V seems to work randomly. I would press it nothing, press it again, nothing, and then I press it a few times quickly and then it pastes three or four copies of the image, but the other side couldn't even see it.
-
Major
commented
@skprufo This is still an issue. You marked this as "fixed" in March of 2017 yet there are multiple open threads (including recent comments on this one!) saying that it's not fixed.