# Resizing large ~16:9 (2688x1520) images for use with yolov5?

**URL:** <https://discuss.roboflow.com/t/resizing-large-16-9-2688x1520-images-for-use-with-yolov5/1416>\
**Category:** 🤝  Community Help\
**Created:** [February 4, 2023, 9:52pm UTC](https://discuss.roboflow.com/t/resizing-large-16-9-2688x1520-images-for-use-with-yolov5/1416 "2023-02-04T21:52:11Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![EvanVanVan](https://avatars.discourse-cdn.com/v4/letter/e/a698b9/32.png) [@EvanVanVan](https://discuss.roboflow.com/u/EvanVanVan)\
**Post date:** [February 29, 2024, 9:17pm UTC](https://discuss.roboflow.com/t/resizing-large-16-9-2688x1520-images-for-use-with-yolov5/1416/7 "2024-02-29T21:17:06Z")

</div>

As I described in the one picture, I manually crop the wide image square (without cropping the one (shorter) dimension). It’s a time consuming process but can be made quicker by loading dozens of images into Photoshop at once, locking the crop aspect ratio to 1:1 and using keyboard shortcuts to save/close the images.

One of the developers got back to me elsewhere and said that manually cropping is a bad idea because that can’t be replicated at runtime. But what really can’t be replicated at run time is taking my widescreen camera image and squeezing it down to a 1:1 aspect ratio. 🙄 (I.e. Training a model with a widescreen-source image using Stretch to: 640x640.)

FWIW, looking at these pictures again, those bounding boxes I used in the examples are terrible and way too big. I am pretty proud of my model though, it can be very accurate with only a couple hundred images per class. Not exactly “[degraded performance](https://discuss.roboflow.com/t/cropping-feature-with-the-annotate-toolset/1497/2)” imo.

---

_[View the full topic](https://discuss.roboflow.com/t/resizing-large-16-9-2688x1520-images-for-use-with-yolov5/1416)._
