I used to have a relatively big pr0n collection on my hard drive. For some reason, I decided to delete it, only to want it back about 3 days later. I got most of it back, but a lot of the files were corrupted. My question is: Is there any way I can find these images on e621, only by knowing its original name that i saved it as, for example "0c83dde6fccd3239ed85cc3c21639ce0.png". I have tried googling it; it worked for some of the images, but most of them it didn't. I'm hoping for answer from an admin/mod telling me how to do so, but I'm also predicting that this could be abused for looking at deleted images (idk how this site works >.>)and I'm just screwed. I would greatly appreciate any help.

If you have it saved on your computer you can find it by going to Google images, clicking the little camera icon on the right and then selecting the file and clicking 'search'.

So far as I know, there is no metatag for file name although there is one for file type, size and ratio, etc. So you could set a date range, file type, and size range to really narrow results.

also, if you know the artist you could narrow even more the results

If you changed the name, then no, e621 can't read your hard drive and magically find the file for you.

If you left the name as its default, however, you can search for the image on e621 with the "md5:" metatag. For example, md5:945bd4b144e8f32304e34c4791ef735f. Or for your example, md5:0c83dde6fccd3239ed85cc3c21639ce0. Just use the filename, sans-extension, as the md5 you're searching for.

Since your example returns no results, either the md5 you pasted was incorrect, or the post has since been deleted.

ikdind said:
If you left the name as its default, however, you can search for the image on e621 with the "md5:" metatag. For example, md5:945bd4b144e8f32304e34c4791ef735f. Or for your example, md5:0c83dde6fccd3239ed85cc3c21639ce0. Just use the filename, sans-extension, as the md5 you're searching for.

thank-you, this solves my problem.

luvdaporn said:
thank-you, this solves my problem.

Actually, this doesn't exactly sound the way i want it to sound. Please know that I am extremely grateful ikdind and you are awesome. I wasn't expecting anyone to actually reply to this thread, and you gave me my answer within the hour. soooo...... thanks again :)

ikdind is correct. You can use the md5: meta-tag to search for an image's MD5 hash. Sometimes it's in the filename, especially if you saved the image from e621 or another similar site. Otherwise, you can get a file's MD5 hash by using a program like this one.

Either way, once you have the MD5, just search e621 for md5:hash_goes_here. Assuming the image was unaltered, hopefully you'll find it. If not, either we deleted it, the image was modified since it was uploaded here, or it was never uploaded in the first place.

To answer your question directly: no, there is no way to find an image based on its filename alone, unless its MD5 hash is in the filename.

tony311 said:
ikdind is correct. You can use the md5: meta-tag to search for an image's MD5 hash. Sometimes it's in the filename, especially if you saved the image from e621 or another similar site. Otherwise, you can get a file's MD5 hash by using a program like this one.

Either way, once you have the MD5, just search e621 for md5:hash_goes_here. Assuming the image was unaltered, hopefully you'll find it. If not, either we deleted it, the image was modified since it was uploaded here, or it was never uploaded in the first place.

To answer your question directly: no, there is no way to find an image based on its filename alone, unless its MD5 hash is in the filename.

yeah, I usually just saved with the default name, so pretty much every image is the MD5 hash. thanks for the info, always nice to learn something.

Test-Subject_217601 said:
If you have it saved on your computer you can find it by going to Google images, clicking the little camera icon on the right and then selecting the file and clicking 'search'.

xLuna said:
also, if you know the artist you could narrow even more the results

forgot to respond to you two. Unfortunately, most of the images are so corrupted that i have no idea what they look like, the only thing that remains is the file name. This also means that uploading them to Google won't work.

luvdaporn said:
Unfortunately, most of the images are so corrupted that i have no idea what they look like, the only thing that remains is the file name. This also means that uploading them to Google won't work.

I suspected that would be the case. That also means the MD5 can't be regenerated with any tools, either. So either the name is right, or the image is lost, sadly.

Edit: And whoops, I'd assumed the images in question came from here, and would thus default to their md5 and filetype extension. Good catch, Tony.

tony311 said:
To answer your question directly: no, there is no way to find an image based on its filename alone, unless its MD5 hash is in the filename.

Do you think a metatag that does just that would be useful?

Oh yes, corrupted *facepalm* heh, sorry. Fortunately I save them with the ID as filename, so if I run into this I know what to do: weep and cry for my stupidity lookup for the MD5 hash and/or ID

Rainbow_Slash said:
Do you think a metatag that does just that would be useful?

I know you asked this to Tony, but I don't think it would be useful. There are a lot of conventions for naming files, so when someone downloads a file from somewhere besides here, it doesn't matter whether they left the filename at the browser's suggested default. There's no guarantee it'll match the name of an otherwise identical file that's uploaded here.

For example, someone who commissions a piece on FA might get a file named "yacht.png". If they upload that straight here, then e6 sees the original name as "yacht.png". Someone who finds the file on FA, though, might see "1339074240.jailbird_yacht.png", and think that should be the original filename.

Name collision is another consideration, but it's probably the case that someone searching for "yacht.png" will only get so many results and be able to quickly sort out which one they really wanted.

Then there's the fact that e6 never shows the original filename. Sometimes it shows up by coincidence in the "source" link, but that's not a guarantee. When someone downloads a file from e6, the filename given to the browser is the md5 checksum of the file, followed by the filetype's extension. As long as the user doesn't change that name (or recalculates the md5 sum with a tool), they can easily find the file here by searching for its md5, regardless of the original filename.

Hopefully I'm being helpful.

Edits: Various minor corrections and clarifications.

That is what I'd assumed. Just thought I'd throw it out there though. Thanks

Well.... I sorted out all the pictures I know are corrupt from the ones that seem to be ok, and am kinda surprised at how many were corrupted; I didn't even get on the computer that much during the 3 days they were deleted, and I especially didn't download anything new. I was able to find 1001 corrupted images out of a total of 2427, corrupted images included. I wonder how long it will take to replace them all?