Useful ratios, not guesswork
Start freeform or switch to 1:1, 4:3, 3:2, 16:9 and 9:16 for profiles, photos, video covers and vertical posts.
Drag the frame, choose a useful ratio, straighten the orientation and export exact pixels. Your original never leaves this device.
Cropping and encoding happen locally. No request contains your image.
Start freeform or switch to 1:1, 4:3, 3:2, 16:9 and 9:16 for profiles, photos, video covers and vertical posts.
Keep the crop’s natural detail or request a precise width and height. Locked dimensions stay proportional.
Send the finished crop straight to compression, format conversion or the app-icon studio through a short-lived local handoff.
Nothing. Editing changes only the preview transform. Export renders a new file, and the source stays untouched on your device.
Almost nobody crops for its own sake. There is a destination with a rule attached: a profile picture that must be square, a header that gets cut off at a fixed height, a print shop that wants exact pixels, a form that rejects anything over a size limit. The useful question is not "what looks good" but "what does the thing I am feeding this to actually require", because that determines the ratio and the export size before you touch the frame.
Removing half the pixels does not halve the file. Compression cost tracks detail, not area, and the busy part of a photo is usually the part you kept. If the goal was a size limit rather than a shape, crop first and then compress, and check the number rather than assuming.
JPEG has no alpha channel. If the source was a PNG with a transparent background, the transparent region becomes solid, and on a coloured page that shows as a white box around your subject. Export PNG or WebP when transparency has to survive.
Asking for an output larger than the crop stretches the pixels you have. Nothing is recovered; edges soften and compression artefacts get bigger along with everything else. If a destination demands more pixels than the source contains, the honest fix is a larger source.