Answer: Hi there @spicyseal!

This is a great idea, and it’s something a few of us on the team have shown real enthusiasm for.

So, we would love to have this, and it would be very cool to have it. We can say for sure it’s something we can certainly play with behind the scenes, so leave it with us for now. We’ll look into it and, hopefully, there will be some news for you soon.

Have a great day! Keep the ideas coming, folks.

Answer: Hey, @richardmurrayhumblr!

This would be very nice to have, but what you request here is not possible, unfortunately. But there is an alternative!

We would suggest that you make a post with the image options, with an option indicator like one, two, three, and four, etc. From here you can then add a poll to the same post with the numbers as the options, like the screenshot below:

We hope this helps, and thanks for your question! Keep ’em coming, people.

Answer: Hi there, @thornhands!

We love this idea! And we totally agree with you—it would be lovely and useful to have.

As it happens, we worked on something like this for a previous Hack Day, but due to some constraints, we haven’t been able to polish it off and ship it yet. We would love to though! Perhaps, with a little luck, we’ll do so if we have bandwidth next year. If there’s news, you’ll get it here and at @changes.

Thanks for getting in touch, and keep the questions coming, folks.

Answer: Hi there, @moxley!

We’re really glad you asked this question, as we love getting the opportunity to share the tips and tricks that are applicable in this area.

First off, here are the rules of our image stretching:

1. On mobile apps and mobile sites, we always stretch images to the full width of the post—since a small image on a small screen doesn’t make for an easy viewing experience.
2. On the desktop site, we only stretch images to the full width of the post if the image is at least 300px wide and/or 600px tall.
3. Any images that are placed side-by-side are always stretched to fit their frames, no matter the image’s dimensions or the viewer’s platform.

However, the vast majority of devices and browsers use antialiasing in their default image scaling algorithms. This, as you point out, doesn’t play nicely with pixel art at all. Boooooo!

So, how can you preserve your sharp pixels with 100% consistency for your viewers? The answer is simply to upscale the image yourself before uploading. To keep the pixels square, you’ll need to resize by factors of 100% (200%, 500%, etc.) and use a simple upscaling algorithm that doesn’t use antialiasing. For example, in Paint.NET’s image resize dialog, you can use “Resampling: Nearest Neighbor”, or in GIMP’s, “Interpolation: None”.

The trick here is to resize your pixel art to dimensions above 540px wide so that every viewer’s device is actually forced to downscale the resultant image instead. That way, instead of the resizing algorithm making up details by blurring the pixels, each original pixel is preserved as a perfect square.

We really hope this helps you and the other pixel artists out there. Please, have a great day, week, and month. No, in fact—a great rest of your Tumblr experience, however long it may last. Of course, if you have any other questions on this subject, we will be happy to answer those too!

Answer: Hey, @guzhu-furen!

So, adding more than ten images in the old editor was actually a bug, and not intended. 

We did raise the limit to 30 in the new editor, but we do not intend to raise it higher at this time.

Thanks for your question, we appreciate it. And keep ’em coming, folks!

Answer: Hi, @azraelreaperx!

So, what we can say first is that this is not supported right now, but we appreciate your question.

But we do have another suggestion. It is almost certain that if you are on a mobile device and have Tumblr installed, you can use the app’s Share function to post to Tumblr without having to download the image. Why give it a go and see what sticks? 

And remember, if that Share option isn’t there, or isn’t working, please file a Support ticket and let us know!

We hope this is of some help, and thank you for your question. Keep ’em coming, folks.

Answer: Hey there, @whotf-invited-moonmoon!

This is something we touched on recently over at @changes, for which the same answer must apply here: we’re aware that this bug is still happening in the Android app, and we’re currently working on a fix for this. We hope to get it out in the next version of the app!

Thanks for your question!

Love,

—Cyle.

Answer: Hey there, @theydjarin!

Thanks for getting in touch here—it was not really a bug, per se, but some processes that were running slow, taking hours instead of half a minute. The issue is now resolved, but please drop a line to support if you still notice any problems!

But the good news is the issue you describe here should be a thing of the past.

Thanks for your feedback, and keep it coming.

Best,

—L

Answer: Hello, @soulofazazel.

Good and bad news here. We can confirm it is indeed planned and remains on our to-do list.

However, we cannot offer anything more concrete than that right, and no real timeframe to speak of. As soon as we know more, you will be the first to know! Thanks for your question.

Best,

—Aaron

Answer: Hey there, @disco-tea!

Not a straightforward answer here. At face value, we certainly hope so. But the problem we have is that the apps don’t pre-upload the images as we do on web. This means the 30 images would be sent on post-save, which… may be an awful lot. It could be something that we could look at in future.

That being said, it’s not on the roadmap right now, so we don’t expect it to happen anytime soon. Keep watch on here, or @changes, for any updates, but we’ll ensure you’ll be the first to know.

Best,

—Javi and Cyle (Tumblr Engineering)