# Optimized / Resized GIFs lose all animation, become still frames

**URL:** <https://meta.discourse.org/t/optimized-resized-gifs-lose-all-animation-become-still-frames/19714>\
**Category:** Feature\
**Created:** [2014 年9 月 6 日 07:17 UTC](https://meta.discourse.org/t/optimized-resized-gifs-lose-all-animation-become-still-frames/19714 "2014-09-06T07:17:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

作者： ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
发布日期： [2014 年9 月 6 日 08:13 UTC](https://meta.discourse.org/t/optimized-resized-gifs-lose-all-animation-become-still-frames/19714/2 "2014-09-06T08:13:45Z")

</div>

1. I don’t think it’s actually the job of the server to resize a giant animated GIF that’s so large it doesn’t even fit in the viewport. That’s a lot of work, particularly if we are preserving animation, and as you noted it can munge the compression.

2. Resizing on the client is not a bad idea, provided we can hard-code the dimensions in the `width` and `height` attributes – resizing “on the fly” and letting the browser decide the width/height leads to bouncing of the page as it shifts to accommodate the unknown (until render time) dimensions).

3. This idea has some merit as well, but seems kind of harsh.. and would be dev work. Maybe if that only kicks in when the animated GIF is so large?

---

_[View the full topic](https://meta.discourse.org/t/optimized-resized-gifs-lose-all-animation-become-still-frames/19714)._