How to save an image in Snagit database?

  • 1
  • Question
  • Updated 6 years ago
Hi! I have opened and edited an image in Snagit Editor from a temporary directory in the local file system:



Now I want to PERMANENTLY store this image in the Snagit Library database, as the local temporary file will be deleted soon.

HOW can I do this?
Photo of PeterBan

PeterBan

  • 109 Posts
  • 11 Reply Likes
  • Hopeful

Posted 6 years ago

  • 1
Photo of Austin Gregory

Austin Gregory

  • 8 Posts
  • 5 Reply Likes
Hi,

From within Snagit Editor, choose File > Save As and save the image to any non temporary location. The new image will appear in your Library.

Does this answer your question?
Photo of PeterBan

PeterBan

  • 109 Posts
  • 11 Reply Likes
No, it does not answer my question. Saving the image to any other location than the default Snagit Library location is potentially dangerous: Maybe after a year I don't remember that those files are part of the Snagit library and could be erroneously deleted.
Photo of Manny Carvalho

Manny Carvalho, Champion

  • 1171 Posts
  • 185 Reply Likes
That doesn't matter because Snagit will remember where it is.  The datastore is for automatically saved files and not for the user.  You really shouldn't save things there. If you want to save images collectively just create a new folder and call it something like Snagit Captures and save your files there.

There's no danger in saving files to any other location.
Photo of PeterBan

PeterBan

  • 109 Posts
  • 11 Reply Likes
I see you don't understand my point. I don't want to save the file inside the Snagit datastore file system location. And saving the file in a custom user folder like Snagit Captures as you suggest breaks the logic of Snagit central data storage at all. Only Snagit should be responsible for the file storage location of images which are represented in the Snagit Library. If this rule of central data storage is not followed then there are many potential problems and errors which could arise which are well known to every system administrator or programmer:

Imagine the user decides to create his custom "Snagit Captures" folder on a disk with partition "M:". It could happen that this partition changes its drive letter or the disk becomes unavailable for any technical reason. The user could possibly not immediately become aware of this, but some weeks later he would wonder why some of the images in the Snagit Library he is looking for (e.g. by searching with keywords) have disappeared. But then it could already be too late. And so on and on.

So the rule is: The instance managing the LOGICAL storage (which is the Snagit Library) must also manage the PHYSICAL storage (which in this context means the file system storage). When this rule is not followed then many problems will arise (for the user).
(Edited)
Photo of PeterBan

PeterBan

  • 109 Posts
  • 11 Reply Likes
Or try this one:

1. The user opens a local .PNG image in Snagit Editor

2. Then he puts some vector objects on it, e.g. step numbers

3. Then he tries to close Snagit Editor

4. Snagit Editor asks whether the changes should be saved

5. The user thinks: Oh yes, let's save the changes

6. The next day the user starts Snagit Editor and must realize that all his vector objects have been flattened. A lot of time loss.

Can you see how the current illogical behavior of Snagit Editor harms the user? The program offers to SAVE an image containing vector objects to a flat image file! The lack of logic here is the missing distinction between SAVING and EXPORTING.
Photo of Manny Carvalho

Manny Carvalho, Champion

  • 1171 Posts
  • 185 Reply Likes
That has nothing to do with the file system.  If you want to save edits then you must save it as a .SNAG file.  Anything else will flatten your edits when the capture is saved.

This is part of the Snagit logic that a user needs to understand in order to make sure one is not surprised by things like this.
Photo of Manny Carvalho

Manny Carvalho, Champion

  • 1171 Posts
  • 185 Reply Likes
Then you have a different understanding than I do of the Snagit Library.  I'm not aware of any central data storage, aside from the datastore, that Snagit manages by itself.  While it remembers where it stores captures it doesn't store them anywhere specifically.

As far as the drives, you are right they could be enumerated differently for some reason.  The fix for that is to label the drives.  That never changes once set.  All my drives have both a letter and a label.  If, in your example, partition M is enumerated differently or becomes unavailable then you will be have significantly greater problems than where your captures are.  A backup of these capture will most likely come in as part of the solution.

As Austin said, File > Save As to a permanent location is the key.
Photo of Kaitlin

Kaitlin

  • 138 Posts
  • 26 Reply Likes
Peter, this was an interesting thread to read through, as I've had the same discussion with a colleague a few times.

Manny is correct in saying that you need to save as a .SNAG to retain editing ability on your files. For that reason, I am going to change this to answered.

However, I want you to know that the team is aware of this confusing part of saving. Others have shared their thoughts here.

This conversation is no longer open for comments or replies.