Why can't I copy an image from Google Docs into SnagIt?

  • 1
  • Question
  • Updated 5 months ago
Why can't I copy an image from Google Docs into SnagIt? I use Ctrl-C, edit copy, and edit webclipboard in Google Docs and tried pasting into SnagIt using File-New-New from clipboard. Nothing happens.
Photo of MathDreamer

MathDreamer

  • 15 Posts
  • 4 Reply Likes

Posted 2 years ago

  • 1
Photo of SactoBob

SactoBob

  • 116 Posts
  • 35 Reply Likes
Just do Edit>Paste. Works for me.
Photo of Luke Griffioen

Luke Griffioen, Employee

  • 711 Posts
  • 175 Reply Likes
Hi,

We did find some issues with getting images from Google Docs and we have addressed them in our 4.1.2 update.
Photo of MathDreamer

MathDreamer

  • 15 Posts
  • 4 Reply Likes
I'm very happy with Sang It 2018. I can now copy from Google Docs or Smart Notebook into Snag It.
And, vice versa. This might not seem like a big deal, but it now works flawlessly and it is a time-saver.
Photo of Colleen Hill

Colleen Hill

  • 1 Post
  • 0 Reply Likes

Is the ability to drop a Snagit screenshot into a Google doc or Google chat a new feature?  I am not able to do that with Snagit10


Photo of dbialer

dbialer

  • 2 Posts
  • 0 Reply Likes
I am not able to copy a google doc graphic in the document  and use New->from clipboard in Snagit 2018 for Mac.  Has anyone else go this working?  
Photo of Luke Griffioen

Luke Griffioen, Employee

  • 711 Posts
  • 175 Reply Likes
Hi,

It looks like our fix from the 4.1.2 update no longer works, so Google must have changed something again. We'll take a look and see what's going on. In my clipboard manager my copied image doesn't appear at all.



It looks like if you paste into Apple's notes app and then copy from there, then it will work in Snagit. Not ideal, but it's a viable workaround for now.
Photo of dbialer

dbialer

  • 2 Posts
  • 0 Reply Likes
Thanks Luke.  That is what I've been doing.  Funny we came upon the same solution.
Photo of Luke Griffioen

Luke Griffioen, Employee

  • 711 Posts
  • 175 Reply Likes
Hi,

This issue should be resolved in our 2018.2.0 release, available today. Let us know if you run into any issues!