Crop AVIF images with exact dimensions or aspect ratio presets (1:1, 16:9, 9:16, 4:5). Preserves AVIF's superior compression quality.
AVIF (AV1 Image File Format) is the AOMedia-standardized still and animated image format derived from the AV1 video codec, with the v1.0.0 specification published February 2019. At matched perceptual quality, AVIF photos run roughly 50% smaller than JPEG and 20-30% smaller than WebP, while supporting alpha transparency, 10- and 12-bit HDR (PQ and HLG transfer functions in BT.2020), and 4:2:0 / 4:2:2 / 4:4:4 chroma subsampling. As of May 2026, AVIF is decoded natively in Chrome 85+, Firefox 93+, Edge 121+, and Safari 16.4+ — around 94% global support per caniuse.
Cropping an AVIF necessarily means decode → trim → re-encode (AVIF has no block-aligned "lossless crop" path the way JPEG sometimes does), so the kept area is recompressed. At high quality settings the perceptual loss is well below JPEG's because AVIF's underlying AV1 intra-frame coding is much more efficient. Common reasons to crop:
<picture> source-selection step.If the source isn't AVIF, use Crop PNG, Crop JPG, or Crop WebP instead. To switch formats while keeping the crop, Convert AVIF to JPG, Convert AVIF to PNG, or Convert AVIF to WebP. To shrink the cropped result further (target file size for an email attachment or PageSpeed budget), pass the output through Compress AVIF.
Pixel dimensions below are the platform's documented recommended size; the AVIF cropper accepts any of these as exact width × height inputs, or you can use the preset ratio and resize after.
| Platform / Use | Aspect ratio | Recommended pixels |
|---|---|---|
| Instagram feed post (square) | 1:1 | 1080×1080 |
| Instagram portrait post | 4:5 | 1080×1350 |
| Instagram Story / Reel, TikTok, YouTube Shorts | 9:16 | 1080×1920 |
| YouTube video thumbnail | 16:9 | 1280×720 (min), up to 3840×2160 |
| Twitter/X in-feed landscape image | 16:9 | 1600×900 |
| Twitter/X header | 3:1 | 1500×500 |
| Facebook shared post | 1.91:1 | 1200×630 |
| LinkedIn page cover / banner | ~4:1 | 1584×396 |
| Pinterest standard pin | 2:3 | 1000×1500 |
| Web hero image (desktop) | 16:9 or 21:9 | 1920×1080 or 2560×1080 |
| Web product card (e-commerce) | 1:1 or 4:5 | 800×800 or 1080×1350 |
| App icon source | 1:1 | 1024×1024 |
| Property | AVIF | WebP | JPEG | PNG |
|---|---|---|---|---|
| Underlying codec | AV1 (AOMedia, 2018) | VP8 (Google) | DCT (1992) | DEFLATE |
| File size (photos, equal quality) | ~50% smaller than JPEG | ~25-35% smaller than JPEG | Baseline | Larger than JPEG |
| Lossless mode | Yes | Yes | No | Yes |
| Alpha transparency | Yes (8-bit) | Yes (8-bit) | No | Yes |
| Bit depth | 8 / 10 / 12-bit | 8-bit | 8-bit | 8 / 16-bit |
| HDR (PQ / HLG, BT.2020) | Yes | No | No | No (limited) |
| Animation | Yes (image sequences) | Yes | No | No (APNG only) |
| Browser support (May 2026) | ~94% (Chrome 85+, FF 93+, Safari 16.4+, Edge 121+) | ~96% | Universal | Universal |
| Encode speed | Slowest (5-10× JPEG) | Moderate | Fast | Fast |
AVIF is the right choice when payload size and HDR matter and your audience is on modern browsers. Stick with JPEG for the broadest reach (legacy browsers, old email clients, some print pipelines) and PNG when you need lossless graphics with transparency that every editor opens.
| Edit | What it changes | When to use it |
|---|---|---|
| Crop | Removes pixels outside a rectangle; aspect ratio can change | Tighter frame, different aspect ratio, cut out background or borders |
| Resize | Keeps every pixel but scales width and height | Same composition, smaller (or larger) dimensions |
| Compress | Re-encodes at lower AVIF quality; pixel grid unchanged | Framing and size are correct but file is still too large |
Cropping discards the pixels outside the selected rectangle, but the kept region is re-encoded into a new AVIF — there is no block-aligned lossless crop path for AVIF the way jpegtran -crop exists for JPEG. At the cropper's default quality the re-encode loss is well below JPEG's because AVIF's AV1-derived intra-frame coding is much more efficient. For pixel-identical output, enable Lossless mode; the file will be larger but every kept pixel is preserved exactly.
Yes. AVIF supports a full 8-bit alpha channel (256 levels of transparency, identical to PNG-24) and the cropper preserves it. Logos, icons, and PNG-style transparent assets stay transparent in the cropped AVIF — no flattening, no white background. If your source has a wider alpha bit depth (rare), the output keeps the same alpha precision as the input.
If your source AVIF is 10- or 12-bit with an HDR transfer function (PQ or HLG, BT.2020 primaries), the cropper keeps the bit depth and color space by default — useful when the input is a screenshot from an HDR phone (recent iPhones and Pixels export HDR AVIFs) or a graded render. You can also explicitly set the Bit Depth in the options if you want to down-convert HDR to 8-bit SDR to maximize compatibility with older viewers.
Yes. Animated AVIFs (image sequences) crop frame-by-frame: the same X, Y, width, and height region is applied to every frame, and the output stays an animated AVIF. Frame count, frame rate, and loop behavior are preserved. If you only need a single still frame, Convert AVIF to PNG extracts one frame at a time.
AVIF uses AV1 intra-frame coding, which is roughly 5-10× slower to encode than JPEG and can be 40-50× slower than WebP at default speed settings. That's the tradeoff for the format's smaller file size. The cropper exposes a Compression Speed option — lower the speed (slower encode, smaller file) for archival or hero images; raise the speed (faster encode, slightly larger file) when turnaround matters more than the last 5% of file-size savings, such as working through a stack of product shots one at a time.
As of May 2026, native AVIF decode is available in Chrome 85+, Firefox 93+, Edge 121+, and Safari 16.4+ — caniuse.com reports about 94% global support. Mainstream legacy environments that can't decode AVIF: IE 11, older Android WebView, and Safari before 16.4 on iOS 15 and earlier. If you need to support those, use the HTML <picture> element to serve AVIF first with a JPEG or WebP fallback, or Convert AVIF to JPG for a static fallback file.
Standard cropping is rectangular only — both AVIF and the cropper produce a solid rectangle of pixels (with optional alpha transparency). For a true rounded-corner or circular mask, use an image editor like Photopea (free, browser-based) or GIMP to apply the rounded shape after cropping, or use a CSS border-radius / clip-path on the rendered web page. For circular profile pictures on LinkedIn, Slack, Discord, or GitHub, a centred 1:1 square is sufficient — those platforms apply the round mask automatically when they display the avatar.
Cropping removes pixels proportionally — a 4000×3000 source cropped to 1080×1080 keeps roughly 9% of the pixel area, and the file usually shrinks 70-85%. But final size also depends on output quality, bit depth, and the visual complexity of the kept region: detailed texture (foliage, fabric, fur) compresses less efficiently than smooth sky or solid background, so two same-pixel-count crops can produce different file sizes. To force a target size, follow up with Compress AVIF and set a target file size in KB or MB.
The crop tool outputs AVIF. To crop and switch formats, run this tool first, then Convert AVIF to JPG, Convert AVIF to PNG, or Convert AVIF to WebP on the cropped result. Alternatively, convert first to your target format and then Crop PNG, Crop JPG, or Crop WebP — the order rarely affects the final pixel quality, but starting with AVIF and converting last keeps your intermediate file smaller.