7:5 and 5:7 images: crop from 3:2, 4:3, 3:4 or 2:3 on Sume
No Sume image row lists 7:5 or 5:7, but BFL's FLUX 3 Image does. How many pixels you lose cropping from 3:2, 4:3, 3:4 and 2:3, with the exact numbers.

If you need 7:5 or 5:7, generate at the nearest listed ratio and crop. FLUX 3 Image is not listed in the Sume image catalog (read 2026-10-09). No Sume row lists 7:5 or 5:7, so they are not among the documented values. From 3:2 you lose about 6 percent of the width, and from 4:3 about 4 percent of the height.
Which ratios does BFL list near 7:5?
BFL puts 7:5 in its landscape photo group with 3:2 and 4:3, and 5:7 in the portrait group with 3:4 and 2:3 (BFL docs, read 2026-10-09). Those four neighbors are all on Sume.
How many pixels does the crop cost?
Using Nano Banana 2.1 2K frames from Google's size table (read 2026-10-09), the crop keeps the full edge on one side and trims the other:
| From | Frame | Result | Trim |
|---|---|---|---|
| 3:2 to 7:5 | 2528x1696 | 2374x1696 | 154 px of width |
| 4:3 to 7:5 | 2400x1792 | 2400x1714 | 78 px of height |
| 3:4 to 5:7 | 1792x2400 | 1714x2400 | 78 px of width |
| 2:3 to 5:7 | 1696x2528 | 1696x2374 | 154 px of height |
Which neighbor should I start from?
Start from 4:3 or 3:4: the trim is 78 px at 2K, about 3 percent of a long edge, which loses less of the composition. The 3:2 and 2:3 crops cost about 6 percent. Say the subject should sit in the middle in the prompt, since the crop removes the edges.
The scale is done in your code. Sume does not apply target_pixels, and it returns the pixels the row produces.
- Compose with a safe margin of at least 5 percent.
- Keep text and logos away from the cropped edges.
- Verify the result size after the crop, not before.
Can the crop be done in code?
Yes: the arithmetic is two lines. This helper prints the output size for a width, height and target ratio.
If 7:5 is a hard requirement for a print order, the cleanest route is to generate at 4:3 or 3:2, crop once and keep the full-size original. A second crop later, for another channel, should start from the original, not from the cropped file. Name the files with the ratio so a 7:5 never gets mistaken for a 3:2.
def crop(w, h, rw, rh):
if w * rh > h * rw: # frame too wide
return round(h * rw / rh), h
return w, round(w * rh / rw) # frame too tall
print(crop(2528, 1696, 7, 5))
print(crop(2400, 1792, 7, 5))
print(crop(1792, 2400, 5, 7))
print(crop(1696, 2528, 5, 7))Sources
Related posts
More in Developers
- 8 avatar videos on a Free Sume workspace: 6 accepted, then 429
A Free Sume workspace runs 1 job, queues 5 and accepts 6. The 7th and 8th avatar video submits get 429 queue_full. A retry loop that waits and reuses the key.
- Eight Wan 3.0 clips on Free: six queue, two get queue_full
Free plan accepted capacity is 6 paid jobs. Submit eight 10-second Wan 3.0 720p jobs and two return 429 queue_full; the six accepted hold $7.50 of the $10.00.
- A 7-second clip on six Sume video models: $0.525 to $4.0446
Per-second list prices times 7 s for six Sume video models, with each model's accepted duration range and a Python check that rejects out-of-range lengths.
- A fresh UUID per retry is not an idempotency key (Node, Sume)
Create the Idempotency-Key once outside the retry loop, retry only 429, 502, 503 and 504, and stop on 4xx. A Node submit helper for Sume /v1/videos.
Written by Sume