Resize a photo without confusing crop, dimensions, and file size

Separate the frame, the composition, and the byte limit

A 1200 × 630 requirement describes the output's pixel dimensions. It does not tell you which part of the original image must remain visible, and it does not guarantee that the file will be smaller than an upload limit. Resolve those three decisions separately: choose the frame, inspect the crop, then check the exported file's bytes.

PicFit supports custom dimensions and multiple preset sizes, Fill and Fit modes, horizontal and vertical focus for Fill, background selection, and JPG, PNG, or WebP export. Image processing runs in the browser. This example uses a 4032 × 3024 landscape source and a custom 1200 × 630 target; it is a geometry example, not a claim about a particular platform's current upload requirements.

Fill: occupy the entire frame and crop the excess

The source has a 4:3 aspect ratio, while the target is 40:21, approximately 1.905:1. Scaling the whole photo to 1200 pixels wide produces a 1200 × 900 image. Filling the 1200 × 630 frame therefore removes 270 output pixels vertically: 135 from the top and 135 from the bottom when focus is centered.

In source coordinates, the scale is 1200 / 4032, approximately 0.297619. The retained height is 630 / 0.297619 = 2116.8 source pixels. The centered source crop starts at y = (3024 − 2116.8) / 2 = 453.6 and keeps the full 4032-pixel width. Fractional source coordinates are sampled during drawing; PicFit rounds its intermediate crop canvas to an integer size before resizing to the exact target.

Fit: preserve the photo and fill the remaining space

Fit uses the smaller scale factor, 630 / 3024, approximately 0.208333. The complete photo becomes 840 × 630 and is centered inside the 1200 × 630 output. This leaves 360 pixels of unused width, or a 180-pixel strip on each side. PicFit fills those strips with the selected background, or leaves them transparent when the output format and preset allow it.

Use Fill when the photo should reach every edge and the subject survives the crop. Use Fit when every part of a screenshot, document, or product image must remain visible. Stretching the original directly to 1200 × 630 would change its proportions; PicFit's Fill and Fit controls avoid that distortion.

Produce a usable export in PicFit

A single focus position is applied across selected sizes, so a crop that works for a wide image may fail for a square or portrait version. Inspect every selected preview before downloading a batch.

1. Open PicFit and choose the original image. Start with the highest-quality source available rather than a previous compressed export.
2. Add a custom size of 1200 width and 630 height, or choose the required preset. Confirm dimensions against the destination's current documentation.
3. Choose Fill for edge-to-edge coverage. Begin with centered focus, then adjust vertical focus if the important subject is too close to a cropped edge. In this example, changing horizontal focus has no effect because the full source width is retained.
4. Choose Fit instead if cropping removes necessary information. Select a background that will look intentional beside the photo.
5. Select JPG, PNG, or WebP. For JPG or WebP, choose an initial quality within PicFit's 60–100 range and download a sample.
6. Inspect the downloaded file at its intended display size and confirm its dimensions and byte size. If it exceeds the destination's limit, adjust the format or quality and export again from the original.

Choose a format that preserves the feature you need

JPG cannot store transparent pixels. PicFit makes JPG output opaque and uses white when transparency is selected without another background. PNG and WebP can preserve transparency, but some PicFit presets deliberately require opaque output. Selecting a transparent background cannot override such a preset.

PNG is useful for graphics and transparency, but a photographic PNG can be much larger than a lossy export. PicFit does not offer a PNG quality slider. WebP supports both lossless and lossy encoding as a format; PicFit exposes browser-based quality export, not a separate guaranteed-lossless WebP switch.

Why fewer pixels do not promise a particular file size

The original contains 12,192,768 pixels; the target contains 756,000. A raw 8-bit RGBA buffer for the target would contain 3,024,000 bytes, but that is not the compressed JPG, PNG, or WebP file size. Flat areas, fine texture, noise, transparency, encoding format, and quality all affect the export. A quality setting of 80 does not mean 80% of the original bytes or a measurable 80% visual fidelity.

PicFit has no exact target-kilobyte control, so verify the downloaded file. Its input limit is 40 × 1024 × 1024 bytes and 40 million pixels. Custom output dimensions must be at least 16 pixels per side and at most 20 million pixels in total. Large inputs and many selected outputs can still exhaust memory on a phone; process fewer sizes at a time if export fails.

Re-exporting a small, blurry image at larger dimensions cannot recover missing detail. Repeated JPG exports can accumulate compression damage. Keep the original and generate each final size from that source. If a transparent export appears black in a particular viewer, inspect it against a checkerboard or another background before assuming the pixels were lost.

Try it in the tools

Technical references

• PicFit: supported formats, limits, and fit modes
• MDN: canvas export formats and quality parameters
• Google WebP documentation: compression and transparency

Found an incorrect result or an unclear step? Send a correction with the input, expected result, and browser version. Do not include private files or credentials.