Two different jobs
Cropping changes framing—what stays inside the picture. Resizing changes pixel dimensions. Stretching with unlocked aspect ratio is usually undesirable. You often need crop and resize together.
Start with destination ratio: square avatars, 16:9 thumbs, and tall mobile banners demand different crops. Set ratio before fine-tuning so platforms do not chop a freeform crop again.
Margins, upscaling myths, sequence
Leave safe margins; platforms re-crop. Keep faces and logos off edges. Include breathing room for product shadows and labels.
Shrinking large photos for the web is normal. Enlarging a 300px icon to a hero invents no detail—it looks soft. Find higher-resolution sources instead.
Recommended sequence: crop to composition and ratio, resize with ratio locked, then compress or convert for delivery.
- Crop for framing
- Resize for pixels
- Compress last
- Keep masters
- Match platform specs
Document scans and masters
Crop desk clutter before image-to-PDF. Straighten when possible. Uneven phone photos become uneven PDF pages.
Exports discard cropped pixels. Keep originals until assets work in context—especially campaigns that may need wider reframes later.
Master framing first and pixel math second so images look intentional in every template.
Field notes for crop and resize images guide
When this workflow matters for school, work, or clients, keep a short paper trail: source file names, settings you chose, and the time you exported. That record turns a confusing revision request into a five-minute fix.
If something fails once, change one variable at a time—file size, format, page range, or compression strength—so you learn which lever actually caused the problem instead of thrashing randomly.
Finally, share only what the recipient needs, and prefer private account storage when you must revisit sensitive outputs. Temporary guest processing is convenient; it is not a long-term archive.
Field notes for crop and resize images guide
When this workflow matters for school, work, or clients, keep a short paper trail: source file names, settings you chose, and the time you exported. That record turns a confusing revision request into a five-minute fix.
If something fails once, change one variable at a time—file size, format, page range, or compression strength—so you learn which lever actually caused the problem instead of thrashing randomly.
Finally, share only what the recipient needs, and prefer private account storage when you must revisit sensitive outputs. Temporary guest processing is convenient; it is not a long-term archive.
Field notes for crop and resize images guide
When this workflow matters for school, work, or clients, keep a short paper trail: source file names, settings you chose, and the time you exported. That record turns a confusing revision request into a five-minute fix.
If something fails once, change one variable at a time—file size, format, page range, or compression strength—so you learn which lever actually caused the problem instead of thrashing randomly.
Finally, share only what the recipient needs, and prefer private account storage when you must revisit sensitive outputs. Temporary guest processing is convenient; it is not a long-term archive.
Field notes for crop and resize images guide
When this workflow matters for school, work, or clients, keep a short paper trail: source file names, settings you chose, and the time you exported. That record turns a confusing revision request into a five-minute fix.
If something fails once, change one variable at a time—file size, format, page range, or compression strength—so you learn which lever actually caused the problem instead of thrashing randomly.
Finally, share only what the recipient needs, and prefer private account storage when you must revisit sensitive outputs. Temporary guest processing is convenient; it is not a long-term archive.
Field notes for crop and resize images guide
When this workflow matters for school, work, or clients, keep a short paper trail: source file names, settings you chose, and the time you exported. That record turns a confusing revision request into a five-minute fix.
If something fails once, change one variable at a time—file size, format, page range, or compression strength—so you learn which lever actually caused the problem instead of thrashing randomly.
Finally, share only what the recipient needs, and prefer private account storage when you must revisit sensitive outputs. Temporary guest processing is convenient; it is not a long-term archive.
Field notes for crop and resize images guide
When this workflow matters for school, work, or clients, keep a short paper trail: source file names, settings you chose, and the time you exported. That record turns a confusing revision request into a five-minute fix.
If something fails once, change one variable at a time—file size, format, page range, or compression strength—so you learn which lever actually caused the problem instead of thrashing randomly.
Finally, share only what the recipient needs, and prefer private account storage when you must revisit sensitive outputs. Temporary guest processing is convenient; it is not a long-term archive.
Field notes for crop and resize images guide
When this workflow matters for school, work, or clients, keep a short paper trail: source file names, settings you chose, and the time you exported. That record turns a confusing revision request into a five-minute fix.
If something fails once, change one variable at a time—file size, format, page range, or compression strength—so you learn which lever actually caused the problem instead of thrashing randomly.
Finally, share only what the recipient needs, and prefer private account storage when you must revisit sensitive outputs. Temporary guest processing is convenient; it is not a long-term archive.