# Onebox Image optimization / caching

**URL:** <https://meta.discourse.org/t/onebox-image-optimization-caching/19843>\
**Category:** Feature\
**Created:** [September 10, 2014, 4:31am UTC](https://meta.discourse.org/t/onebox-image-optimization-caching/19843 "2014-09-10T04:31:35Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Lid](https://avatars.discourse-cdn.com/v4/letter/l/2bfe46/32.png) [@Lid](https://meta.discourse.org/u/Lid)\
**Post date:** [September 10, 2014, 4:31am UTC](https://meta.discourse.org/t/onebox-image-optimization-caching/19843/1 "2014-09-10T04:31:35Z")

</div>

Continuing the discussion from [Image optimisation (work in progress)](https://meta.discourse.org/t/image-optimisation-work-in-progress/6013/2):

> [@zogstrip](#):
>
> Yeah.. sorry for forcing you to disable my _buggy_ implementation…
> 
> I’ll work on your TODO list in order to make it fast & reliable 😉
> 
> One question: what about images in oneboxes? I think we should also optimize & cache them. What do you think?

The following onebox, The image that is loaded as a thumbnail is 2500x1667 **4MB**

[http://www.wired.com/business/2013/03/five-google-products-at-risk/](http://www.wired.com/business/2013/03/five-google-products-at-risk/)

Facebook approach isto serve image via a safe\_image.php script will cache and resize the original image to a manageable thumbnail size.

onebox should be able to cache / resize external images if needed.

---

_[View the full topic](https://meta.discourse.org/t/onebox-image-optimization-caching/19843)._