Hi Marco,

Indeed, you found the relevant thread which I was going to link you to.

The image service got a pretty major upgrade this week and I haven't decided what new sizes (if any) will move over to the officially supported list. What I did do, which is why you noticed the change is remove sizes that aren't used by TMDb in any capacity and that are not on the list of official sizes.

To help me understand someone else's requirements, when you say "normalized", I take it that you're interested in a locked aspect ratio like the 300x450 size that tries to centre crop data (whether it's faces, or text, etc...)?

Hi Travis,

• I think 'Normalize' isn't the right word but what I meant was to make the sizes (more or less) the same in all categories up to a certain maximum. (The only weird ones would then be w342 in posters and h632 in profiles.)

• Perhaps also adding a size like w1920 in backdrops would be very welcome since these days, 1280 isn't very large anymore.

It would never be perfect for everyone but as long as there is a wide range, I can pick the closest above the desired size and slightly crop them by using width= and height= without too much impact on performance.

So roughly, it would then look something like this:

"backdrop_sizes": [
      "w45",
      "w92",
      "w154",
      "w185",
      "w300",
      "w500",
      "w780",
      "w1280",
      "w1920",
      "original"
    ],
    "logo_sizes": [
      "w45",
      "w92",
      "w154",
      "w185",
      "w300",
      "w500",
      "original"
    ],
    "poster_sizes": [
      "w45",
      "w92",
      "w154",
      "w185",
      "w300",
      "w342",
      "w500",
      "w780",
      "original"
    ],
    "profile_sizes": [
      "w45",
      "w92",
      "w154",
      "w185",
      "h632",
      "original"
    ],
    "still_sizes": [
      "w45",
      "w92",
      "w154",
      "w185",
      "w300",
      "original"
    ]

• As for locking aspect ratios with faces etc... if that's a replacement for wxxx_and_hyyy_bestv2 but now officially supported, that would be great. I find it very useful.

As for standards there, perhaps it's an idea to use widths as above and lock them in common aspect rations like 4:3, 3:2, 5:3, 5:4, and 1:1.

Hi, I also noticed that today!

Maybe these changes rise few problems For me I used image width 130 150 300 500 1280. After of actors / movies updates that run by my code through TMDB API, some of them images displayed on my site as broken (because some size of images are not supported any more)

Travis, when you inform us about new supported sizes for all type (Persons, Movies, Scenes) ? For me I have to update my website code to solve all the problems above. I think there are a lot of websites to have the same Issues

Kostas.

@MarcoTC I'll definitely have a look but won't have time to add anything for a bit. I need to think about how and what to make public. You have to remember each size can add quite a bit of extra load to our service (almost 2 million images per size).

@konapaz When I have new sizes to announce I can mention it here but as I mentioned above, it's not immediately planned.

Ah, I understand. That's a lot to store.

I was under the assumption that they were resized on the fly and once done, they would hang out in the local and CDN caches.

Good to know. I'll try to stick more to the standards from now on. :)

Thanks!

So, which sizes I should use in longterm, original? Thanks

Everything found in the configuration method is and has always been officially supported. Everything else isn't.