Image geometry decisions
Crop, fit, padding, and focal points: choose the least destructive image change
A target width and height do not tell a tool what to do with the source edges. The important decision is whether to remove edges, preserve every edge with padding, avoid enlargement, or accept geometric distortion.
On this page
Start with the aspect-ratio mismatch
When source and destination ratios differ, one of four things must happen: an edge is removed, blank space is added, a dimension remains smaller than requested, or the source geometry is stretched. A good workflow makes that tradeoff explicit before it creates an output.
The source subject matters more than the name of the fit mode. A product photo may tolerate a crop; a signed form, a screenshot, or a document image may not.
| Method | What it protects | What it changes |
|---|---|---|
| Crop to fill | The destination canvas and a chosen focal area | Outer source edges are removed |
| Fit with padding | Every source edge | Adds visible background or transparent space |
| Scale down only | The original geometry without enlargement | May not meet a larger fixed canvas |
| Stretch | The exact destination rectangle | Changes the visible proportions of the source |
Try it with a safe sample
Crop or keep the whole picture?
Both results are 600 × 600 pixels. The red and white edge markers make the difference easy to see.
- Download the landscape sample and choose a 600 × 600 canvas.
- Export once with Crop and once with Fit and a white background.
- Compare the edges. Crop fills the square; Fit keeps the full picture.
| Original dimensions | 1,600 × 1,000 px |
|---|---|
| Crop output | 99,955 B |
| Fit output | 41,337 B |
| Both output dimensions | 600 × 600 px |
Crop removes content at the edges. Fit adds space. The tool warns about these changes; neither result stretches the picture.
How we checked this
Synthetic samples. No personal files. Results can vary with browser encoders.
Tested: · Chromium 149.0.7827.55
Download measurements and file hashes · Testing method
Sample files are free to reuse under CC0.
Use a focal point as a reviewable choice
A focal point is not an AI guess. It is a human instruction about the part of the source that should survive a crop or sit within padded space. Aftermath’s anchor controls make that instruction visible, including a per-file override when a batch contains different subjects.
The useful review is visual: compare the source and preview, then ask whether the crop removes a face, a line of text, a signature edge, a UI control, or another required element.
- Use one shared anchor only when the batch has a genuinely shared composition.
- Use per-file overrides for mixed portrait, landscape, and screenshot batches.
- Treat enlargement and stretch warnings as decisions to review, not quiet defaults.
Padding is content, not empty space
A padded image can be the safest option when every edge matters, but the padding becomes part of the final asset. Its colour, transparency, and contrast can affect how a destination or viewer presents the result.
JPEG cannot keep transparent pixels, so a transparent-looking padding choice becomes a solid background in JPEG. A result receipt should make that format change visible before download.
The most common failure is a technically correct but visually wrong image
A file can have exact pixels and bytes while the required content is clipped, distorted, or unreadable. That is why a preview and a measurable result belong together: the numerical check prevents one class of rejection, while human review catches the other.
Desktop tools and commands
Use a local tool