Topic: Obtaining the highest-resolution images from Tumblr

Posted under General

rysyN said:
Make sure you remove the numbers sub-domain. Anything prior to a certain date will 404.

that would explain why that fails when i sometimes visit a tumblr pic.

Updated by anonymous

Now here's an interesting situation. I uploaded post #1337978 from the artist's Tumblr, on which the raw version is 1280 pixels wide. But afterwards, when I was checking other sites to list as sources, I noticed that the artist uploaded a much larger version there, 2200 pixels wide.
The thing is, the image itself was heavily upscaled by the artist either when he colored it or when he edited the text- compare it to post #1337999, an earlier version of the image. The smaller resolution version, post 1337978, appears upscaled as well. Should it still be deleted and replaced with the larger version from IB?

Updated by anonymous

Penguinempire-Dennis said:
Now here's an interesting situation. I uploaded post #1337978 from the artist's Tumblr, on which the raw version is 1280 pixels wide. But afterwards, when I was checking other sites to list as sources, I noticed that the artist uploaded a much larger version there, 2200 pixels wide.
The thing is, the image itself was heavily upscaled by the artist either when he colored it or when he edited the text- compare it to post #1337999, an earlier version of the image. The smaller resolution version, post 1337978, appears upscaled as well. Should it still be deleted and replaced with the larger version from IB?

Using thumbnails in the middle of the text makes your message much less readable. Also this isn't exactly the fault of tumblr raw stuff.

There have been couple similar cases I have seen where artist themselves for whatever reason upscales the content themselves. Other one was luckily exact multiplier nearest neighbor so it could still be fixed easily. But just like with massive compression, it can get deleted even if it was done by artist.

I can see actual additional detail in stuff added into the image after the original version, so even if the base content is upscaled, the coloring and text are actually proper resolution. I would almost like to say this is almost acceptable because of that fact and because it's still artist doing it. In this case the tumblr raw is downscale of that upscale, so inkbunny version is preferred. Just tag it with upscale and put original as parent post.

Updated by anonymous

Updated by anonymous

Munkelzahn said:
Direct image link:
https://68.media.tumblr.com/8ad1cd85f5095d31600eabccd23e1a30/tumblr_oclfqmSkxu1vbxsy5o1_500h.jpg

That's strange, it seems as though the 'h' signifies that only height is restricted to 500 pixels, while the width can be whatever (presumably up to maximum).

While that is an interesting observation, it is still clear that the raw version (1920 x 623) is higher quality. All this changes, as you say, is the raw version redirection plugins that people use, as the extra character ('h') must be removed. I'll see if I can edit the current script to address this issue myself.

EDIT: I made a hotfix for the script, it's pretty simple, you can grab it here. I'll also let the original author know so they can make a proper update.

Updated by anonymous

To-mos said:
This trick doesn't work at

Both those links work for me, and the userscript I have turned the former into the latter just fine.

Someone else reported similiar problems: https://e621.net/forum/show/243758

I had problems with raw links a while back that turned out to be a browser extension. Might be worth checking for you.

Updated by anonymous

To-mos said:
This trick doesn't work at

I've had that problem as well, a workaround that's worked for me is using a proxy. I'm not sure why, but if I get a 404 error attempting to load a raw url, going through a proxy lets me load it fine.

Updated by anonymous

The link that isn't working for To-mos is also not working for me and I'm the one who made the other topic. Seems like we're having the same problem.

Updated by anonymous

Ok this is interesting. I tried it with a proxy server as JAKXXX3 suggested and got different results. The EU server still got 404 but the US server finally loaded it.

Results
https://image.prntscr.com/image/yudYMB-PQUK0rivND7upcA.png

Now the below image, I can't seem to get working after disabling everything and using multiple proxy sites. While the above one finally worked. This is strange.

Orig
https://78.media.tumblr.com/fd6a66aeebfe4fc0e0b88ebe57dea239/tumblr_oxqaf3rIKr1rsowjpo1_1280.png

RAW
https://media.tumblr.com/fd6a66aeebfe4fc0e0b88ebe57dea239/tumblr_oxqaf3rIKr1rsowjpo1_raw.png

Results
https://image.prntscr.com/image/pSlAk4RmTBKZSByF604e2g.png

EDIT: After I looked around I came across https://e621.net/forum/show/243758?page=1

where a user states

plsignore said:
The new workaround appears to be changing 'media' to 'data'
e.g.

https://media.tumblr.com/229d86359d9e7da34196e9939b270e48/tumblr_oxhlpu0dFA1vjc3oio1_raw.png

gives me a 404, but

https://data.tumblr.com/229d86359d9e7da34196e9939b270e48/tumblr_oxhlpu0dFA1vjc3oio1_raw.png

works.

Fucking tumblr I swear...

This fixed it for me. Until next time keep those paws movin'!

PS: I wrote a regular expression with two capture groups for any scripters out there who want to use this to quick replace the "78.media" and "_[numbers].jpeg" parts

/http(?:s)://(\d*.media).tumblr.com/[a-z0-9]*/tumblr_[A-z0-9]*_([0-9]*).jpg/g

Updated by anonymous

KiraNoot said:
data.tumblr.com throws certificate errors. The canonical url for that is https://s3.amazonaws.com/data.tumblr.com/ which means that https://media.tumblr.com/607edc95dc02a676405d66e3f82fe746/tumblr_oxoxuvLXbc1tv4a0ho1_raw.png becomes https://s3.amazonaws.com/data.tumblr.com/607edc95dc02a676405d66e3f82fe746/tumblr_oxoxuvLXbc1tv4a0ho1_raw.png

How do you _raw'ify this Tumblr post?
forum #243192

I keep getting errors when I try.

Updated by anonymous

Thanks for this thread, I uploaded my first image with data.tumblr and raw file! (Added tons of tags, too) Let me know if I did ok.
Question, what's the first source I should list? The raw file, or the tumblr post itself?
EDIT: Actually, since the canonical URL is s3.amazonaws.data.tumblr, should I redo my upload???

Updated by anonymous

BlueMoonstruckWolf said:
EDIT: Actually, since the canonical URL is s3.amazonaws.data.tumblr, should I redo my upload???

No. Source, tags and parent post ID can all be changed after upload by anyone. As for source, the most important one is the submission page, so in this case it's permalink to blog post itself. Other sources are secondary, not entirely necessary, but always good to be there.

Also with direct URL, usually what matters the most is filename and as the front bit isn't required to access the content, it shouldn't matter. You may get browser error if trying to access the image trough SSL, but that can be skipped easily.

Updated by anonymous

BlueMoonstruckWolf said:
Thanks for this thread, I uploaded my first image with data.tumblr and raw file! (Added tons of tags, too) Let me know if I did ok.
Question, what's the first source I should list? The raw file, or the tumblr post itself?
EDIT: Actually, since the canonical URL is s3.amazonaws.data.tumblr, should I redo my upload???

The files in both URLs are the same, just edit the source link to s3.amazonaws.com and you should be fine.

For sources I would recommend in this order,

  • Post link
  • Gallery link
  • Direct-link (raw file)

Updated by anonymous

Geez, no wonder my upload ratio is getting obliterated. :v

Updated by anonymous

Ashram said:
Geez, no wonder my upload ratio is getting obliterated. :v

Your upload ratio went down 22% at worst.

If it becomes a problem you can message an admin about it.

Updated by anonymous

delishop said:
Its rare but sometimes there are images with this URL
http://78.media.tumblr.com/tumblr_mbxys5SQC51rd8tfco1_1280.png
and the changing it to
http://data.tumblr.com/tumblr_mbxys5SQC51rd8tfco1_raw.png
doesn't work. Thankfully some are below 1280px width.

http://lmsketch.tumblr.com/post/33643830852
Posted october 2012, it has already been established that that old posts do not have raw variation.
https://e621.net/wiki/show/howto:sites_and_sources#tumblr

Updated by anonymous

Are there any plans to run a script to change existing URL fields?

If possible, it'd be nice to automatically convert-
//media.tumblr.com
-to-
//s3.amazonaws.com/data.tumblr.com
-so the post links to the correct source. I'm not sure whether a user could automate this, or whether admin action would be required.

Updated by anonymous

Strongbird said:
Are there any plans to run a script to change existing URL fields?

If possible, it'd be nice to automatically convert-
//media.tumblr.com
-to-
//s3.amazonaws.com/data.tumblr.com
-so the post links to the correct source. I'm not sure whether a user could automate this, or whether admin action would be required.

I would almost just left them be.
As long as original blog post url is there content can be found, with direct URL most important part is the filename (and that's why inkbunny, pixiv, etc. are still important even though they give 403 errors when accessed directly) which doesn't change anyway (neither should MD5 string), you can still change it manually yourself and if history repeats itself, they could maybe need to be changed again.

Of course if someone does bot those I'm not opposed.

Updated by anonymous

Does this script cover all possible variations in Tumblr links?

// ==UserScript==
// @name         Raw Tumblr
// @namespace    http://www.munkelzahn.horse/
// @version      0.1
// @description  Convert direct image links on Tumblr to _raw links
// @author       Munkelzahn
// @include      /^(https?:\/\/\d+\.media\.tumblr\.com\/)([a-z0-9]+\/tumblr_)(inline_)?([a-zA-Z0-9]+_)(\d+[a-z]?)(\.[a-z]+)$/
// @grant        none
// ==/UserScript==

(function() {
    var regexp = /^(https?:\/\/\d+\.media\.tumblr\.com\/)([a-z0-9]+\/tumblr_)(inline_)?([a-zA-Z0-9]+_)(\d+[a-z]?)(\.[a-z]+)$/;
    window.location.href = document.URL.replace(regexp, "https://s3.amazonaws.com/data.tumblr.com/$2$3$4raw$6");
})();

It converts regular links:
http://78.media.tumblr.com/d63563ab3c01142db67eb7055a78f89a/tumblr_ozbskqYvLC1tdkn7oo1_1280.jpg
Inline links:
http://78.media.tumblr.com/fa93c8a9d137fff645055bdc9e2f8ce9/tumblr_inline_ozd3whC0oS1t658or_500.png
Links with h after the resolution:
http://78.media.tumblr.com/f3709a8d257e73de3b31bc2654cdd0c3/tumblr_oj4qqiPX0R1t8icefo1_500h.jpg

Updated by anonymous

Lance_Armstrong said:
This is just speculation, but maybe "revision1" for an edited image?

Definitely. Anything with dialogue will often be edited after being posted -- no one is safe from typos and spelling mistakes.

Also resolves perfectly fine to-
https://s3.amazonaws.com/data.tumblr.com/2253ed455d4c0c1cac937767d400f0a4/tumblr_ozakf55XJp1r4eyo7o1_r1_raw.png
-wherein removing _r1 causes a broken URL, so it's part of the filename if anything.

Updated by anonymous

Anyone know if there’s a good way to get the raw images on mobile, specifically iOS?

Updated by anonymous

Dyrone said:
Anyone know if there’s a good way to get the raw images on mobile, specifically iOS?

Is it not possible to edit the url on IOS?

Updated by anonymous

Peekaboo said:
Is it not possible to edit the url on IOS?

Of course it is...but have you seen how complex that is nowdays? It’s not as simple as changing the “1280” to “raw” and calling it a day.

Updated by anonymous

Hey, it's not exactly the same site, but there's soup.io as well. If you look at this link the actual picture is hidden on the other site "Just in case", but I cannot seem to figure out what the optimal resolution is. I have located a 1280 on another tumblr, but just in case this can go even higher I'll wait on it.

Updated by anonymous

Dyrone said:
Of course it is...but have you seen how complex that is nowdays? It’s not as simple as changing the “1280” to “raw” and calling it a day.

Assuming you’re using Safari not the tumblr app, if you have an iPhone 6S or later, 3D Touch on the picture and it will open with the URL, so now you can edit the URL to raw. If you don’t have a 3D Touch capable iPhone, use the Chrome browser. In Chrome, hold down on the picture and tap Open in new tab.

Updated by anonymous

Dyrone said:
Of course it is...but have you seen how complex that is nowdays? It’s not as simple as changing the “1280” to “raw” and calling it a day.

save the necessary url parts in notepad and copypaste them from there. or simply memorize the url parts like i did

Updated by anonymous

Furrin_Gok said:
Hey, it's not exactly the same site, but there's soup.io as well. If you look at this link the actual picture is hidden on the other site "Just in case", but I cannot seem to figure out what the optimal resolution is. I have located a 1280 on another tumblr, but just in case this can go even higher I'll wait on it.

soup.io does dynamic rescaling, you can put in any number and it rescales the image to that resolution. Avoid soup.io, because you cannot access the original image at all.

Updated by anonymous

KiraNoot said:
soup.io does dynamic rescaling, you can put in any number and it rescales the image to that resolution. Avoid soup.io, because you cannot access the original image at all.

Well, is this edition uspcaled? It's the highest resolution I can find, but if it became so from upscaling then it's for naught.

Updated by anonymous

Furrin_Gok said:
Well, is this edition uspcaled? It's the highest resolution I can find, but if it became so from upscaling then it's for naught.

Deleting the value alltogether seems to give version where there's no visible scaling going on: http://asset-c.soupcdn.com/asset/13944/6942_cf61.jpeg
Usually these sites as they use that value as multiplier, removing it or setting it to 0 usually gets you at least closer to original.

Sadly can confirm what Kira said that you can just input massive numbers and the site will upscale the content for you. Largest version I can get from there is 4000x3556, which is incredibly clear upscale, but where it's possible to somewhat calculate from pixels that it has been upscaled by 3-4 times, which would fit the above links resolution.

If I compare this version to the tumblr you linked, that tumblr version does seem upscaled and more compressed.

Updated by anonymous

Mario69 said:
Deleting the value alltogether seems to give version where there's no visible scaling going on: http://asset-c.soupcdn.com/asset/13944/6942_cf61.jpeg
Usually these sites as they use that value as multiplier, removing it or setting it to 0 usually gets you at least closer to original.

Sadly can confirm what Kira said that you can just input massive numbers and the site will upscale the content for you. Largest version I can get from there is 4000x3556, which is incredibly clear upscale, but where it's possible to somewhat calculate from pixels that it has been upscaled by 3-4 times, which would fit the above links resolution.

If I compare this version to the tumblr you linked, that tumblr version does seem upscaled and more compressed.

Alright, thanks for helping.

Updated by anonymous

slyroon said:
Does anybody know how to get the tumblr link from this furaffinity link?

http://d.facdn.net/art/marjani/1435966486/1435966486.marjani_https_3a_2f_2f40.media.tumblr.com_2fa9902edb8837f4fa605323cab57b73fc_2ftumblr_nqw7e0f5bt1sl2eueo1_1280.png

Hmm... is there any way to search for such files using FA's search? I tried @filename media&@filename tumblr, 2ftumblr and many others, no success so far. The query @filename tumblr works somewhat, but produces way too many false positives (filename with the second id isn't enough to get the download link, you need both ids) and definitely some false negatives (Marjani's post isn't included if I add @lower marjani).

Not that it would be very useful, as Tumblr blogs are rarely secret, but I'm curious anyway. 🙄

Updated by anonymous

plsignore said:
TL;DR if you're saving images from tumblr, change "1280" to "raw" in the url first!

I have a hunch most images uploaded here which come from tumblr are shrunken.

Yeah, but that’s why the “resize image” is there.

Updated by anonymous

Mairo said:
...where?

My bad, I meant the “resize image” button on the post. I was saying that under the options of a post that the button helps enlarge the post so it doesn’t matter if the post was shrunken from tumblr, if I’m wrong I apologize.

Updated by anonymous

IllinoisBoi1 said:
My bad, I meant the “resize image” button on the post. I was saying that under the options of a post that the button helps enlarge the post so it doesn’t matter if the post was shrunken from tumblr, if I’m wrong I apologize.

This is at the level that let me break it down for smaller pieces. You are wrong, but only because you are looking at it from your own angle as user who views content here.

Yes, this site will also serve you downscaled content according to your user settings.
Samples (default to guests and new users) will show you 800x800 restricted JPG of the image until you click to see full image or download. Dynamic scaling (default for older users) will limit the resolution of the image to fit page horizontally until you click full size or download. You can check your user settings to see these and toggle it if you want to.

However the problem here is that you can create 800x800 pixel image from e.g. 3000x3000 pixels large image, but you will never ever get that original 3000x3000 from that 800x800 ever. This is the problem and this is why the tumblr situation was so huge deal, because up to this point everyone was uploading 1280x1280 pixel sized resized versions of much larger images. At this point you have to distinguish that even if this doesn't effect you personally as individual user right now, this does have much more to it which will effect others now and might even effect you in future, wouldn't be first time when someone ripped all their CDs at 128kbps WMA files.

One of the goals of this site is to archive, to have highest quality variation stored. That means that if there is that 3000x3000 available, that should be the version that is in here as well, not the 1280 version and 800 version is automatically created for users who want to view content without worrying content scaling out of bounds or draining their data caps.

Updated by anonymous

Ok, apologies for the stupid question, but when i change the ''1280'' value to ''raw'' i get the ''There's nothing here.'' notification. I presume that we use ''upload from url'', correct?

Updated by anonymous

Haljkljavahlibrz said:
Ok, apologies for the stupid question, but when i change the ''1280'' value to ''raw'' i get the ''There's nothing here.'' notification. I presume that we use ''upload from url'', correct?

only changing the number to raw is not enough. you also need to change the *number*.media in beginning to s3.amazonaws.com/data

Updated by anonymous

Lord_Eggplant said:
only changing the number to raw is not enough. you also need to change the *number*.media in beginning to s3.amazonaws.com/data

Ok, thanks a lot for clarification :)

Updated by anonymous

So, just by accident, I found out "a.tumblr.com/" works and takes you to the raw image file. How does this site even function?

Updated by anonymous

delishop said:
So, just by accident, I found out "a.tumblr.com/" works and takes you to the raw image file. How does this site even function?

So rather than s3.amazonaws.com/data.tumblr.com we can shortcut it as a.tumblr.com? Wow.

Updated by anonymous

Weird, I still use data.tumblr without the amazon bit and it works fine.

Updated by anonymous

Ashram said:
Weird, I still use data.tumblr without the amazon bit and it works fine.

It works, but SSL certificate won't match, so if you are trying to access the image trough SSL (https:// beginning) and using certain browsers like Chrome, you will get big warning messages doing that.

So you need to either bypass the warning with multiple clicks, use the domain where the certificate belongs to or access the page trough non-secure connection.

And in the year 2018, SSL connections should be norm, no matter what furaffinity says, them still defaulting to non-secure connection.

Updated by anonymous

Looking back, had I known this sooner, or had I have been more active on this site, this wouldn't've been a hassle, especially when posting a better version.

In my defense regarding on posting my own art from Tumblr from 2016 onwards, that was the time when I left FA for 2 years, and I didn't know that Tumblr had raw image back then.

Updated by anonymous

delishop said:
So, just by accident, I found out "a.tumblr.com/" works and takes you to the raw image file. How does this site even function?

There’s something here.

Updated by anonymous

Olscli16 said:
404 not found. -_-

That's extremely helpful comment which is surely to get extremely helpful responds, especially when not even the most essential amount of information has been given to even help.

Another favorite is "This doesn't work for me" on videos, but at least with those I do have access to the video itself.

Updated by anonymous

first, a.tumblr.com then, raw. then? It works!

Updated by anonymous

Olscli16 said:
first, a.tumblr.com then, raw. then? It works!

Thanks a lot!

By the way, is there a similar method do obtain the full resolution images from Blogspot pages as well?
Looks like I can't get any higher resolution than 1600 pixels...

Updated by anonymous

disko said:
Thanks a lot!

By the way, is there a similar method do obtain the full resolution images from Blogspot pages as well?
Looks like I can't get any higher resolution than 1600 pixels...

howto:sites_and_sources#blogger

Updated by anonymous

Thank you Mairo.

Unfortunately this method doesn't seem to work with images from posts that are several years old. For example, I tried it in some images that were posted back in 2010 and still the best I can get is the 1600px image. Could it be that back then high-resolution images were being resampled by default at 1600px upon upload? Has anybody else noticed that with images on old Blogspot posts?

If anybody knows any workaround on this please let us know.

Updated by anonymous

disko said:
Thank you Mairo.

Unfortunately this method doesn't seem to work with images from posts that are several years old. For example, I tried it in some images that were posted back in 2010 and still the best I can get is the 1600px image. Could it be that back then high-resolution images were being resampled by default at 1600px upon upload? Has anybody else noted this with images on old Blogspot posts?

If anybody knows any workaround on this please let us know.

Can you provide a link?

Updated by anonymous

disko said:
Sure. Take for example the images on this post: http://junioracting.blogspot.com/2010/11/interview-i-scanned-from-cambridge.html

By clicking on them you get the 1600px image, but even if you change s<width> from s1600 to s0, you still get exactly the same image.

That possibly just means the person who posted the image legitimately had the image that size when posting. The pages are definitely readable at that size.

Updated by anonymous

I doubt that. I've seen the same thing happening in several other posts from that time as well; they only go up to 1600px. The images on those posts are another example:

http://hlundqvist.blogspot.com/2012/04/henrik-lundqvist-king-magazine-scans.html

http://junioracting.blogspot.com/2010/11/this-is-interview-with-renowned.html

I don't think that all uploadeders would resize their images to 1600px specifically before posting them. What seems more likely is that quite simply Blogger was set to resample all high-resolution images to 1600px in order to save space.

Updated by anonymous

disko said:
I don't think that all uploadeders would resize their images to 1600px specifically before posting them. What seems more likely is that simply Blogger was set to resample all high-resolution images to 1600px in order to save space.

This could be the case, haven't looked too much into it as not many artists use this site for anything, but in all cases if there has been higher quality version, replacing the width indicator with 0 has worked.

Updated by anonymous

Dyrone said:
2. So I'm just screwed pretty much?

In this case, yes, 500px is maximum width you will get out of that one.

Updated by anonymous