Why 1200×628 appears on checklists
Portals, ad specs, and CMS presets cite 1200×628 because their layouts assume that grid. Open Graph cards assume a wide 1200×628 grid, close enough aspect ratios still crop unpredictably in link previews. Start from the original export whenever you can; chat-downloaded copies often arrive already soft. Open the download once before you close the tab. Being under the cap is the real pass condition; exact byte matching is uncommon.
Source masters that survive downscaling to 1200×628
Start from a larger master when possible; upscaling a tiny source makes edges fuzzy even if pixels match. Start from a larger master when downscaling; upscaling tiny logos cannot invent crisp edges at OG width. Keep an uncompressed master until acceptance is confirmed. Stacked lossy passes look worse on each retry. Avoid screenshotting the preview pane, download the generated file instead. If the result looks too soft, tighten framing before lowering quality again.
Title safe zones on link preview art
Keep headlines out of the bottom third where platforms overlay domain labels on some clients. High-contrast badge lettering survives better than thin scripts at tight caps. If rejection continues, re-read the help text for a second hidden rule. Temporary processing is not archival storage, save the download you intend to submit.
JPEG output for OG weight discipline
Default JPEG output keeps bytes practical for photo content. Flat marketing PNGs may flatten to JPEG here when photo weight must drop. Copy the exact help-text number when switching pages. Neighboring tools look similar but can still fail validators. Preview against both light and dark backgrounds when edges or transparency may change after encoding. Width and height on the result card update whenever the engine changes dimensions.
Social KB caps after OG pixel fit
Email and CMS fields sometimes add hundred-kilobyte limits after pixel rules, chain compress tools when both appear. Very large source dimensions fight small byte budgets; the engine may reduce width and height when quality alone fails. If rejection continues, re-read the help text for a second hidden rule. Landing under the published maximum usually beats chasing an exact byte count.
Batch campaign OG variants
UTM-specific art still needs per-file preview, text placement differs when logos move. Each file gets its own result card. Review every preview before submitting a folder of applicants or SKUs. Preview against both light and dark backgrounds when edges or transparency may change after encoding. If the result looks too soft, tighten framing before lowering quality again.
Validate OG pixels before ad launch
Download once and inspect at 100% zoom; soft text fails CTR tests even when dimensions match 1200×628. Pixel boxes and kilobyte caps are independent validators, satisfying one never excuses the other. Evenly lit, face-forward crops usually survive tighter budgets better than wide scenes. Temporary processing is not archival storage, save the download you intend to submit.
How the resize is applied
Output is written at 1200×628 pixels. The preview and download use that raster. File weight still depends on subject detail and the output format, not only the pixel box.
Resize checks
Exact-size tools are checked by measuring the output width and height after processing. A pass means those pixels match the named box. File size is reported separately. Reviewed 5 October 2026.
Technical reference
Pixel dimensions are the width and height of the raster. File size is a separate property driven by compression and detail. MDN’s image format guide is a clear starting point: image types on MDN.
Frequently asked questions
Must OG images be exactly 1200×628?
Output targets that OG box; fit modes may letterbox, read final pixels on the card. Neighboring tools exist for nearby sizes; switching is better than forcing the wrong ceiling.
OG resize alone satisfy KB limits?
Not always, compress when portals publish kilobyte caps after pixel rules. Batch mode still shows per-file previews. Review each result before submitting a set.
Upscale tiny OG art to 1200×628?
Upscale is soft, design at or above OG width when possible. Measured bytes on the result card come from the generated file, not a simulated estimate.
Orientation tags after OG resize?
Preview visually; tags may not match post-encode display. JPEG target-size encoding is lossy; the preview exists so you can judge tradeoffs honestly.
Batch OG images at 1200×628?
Independent previews per campaign asset. Open the download once on your submission device before retrying the portal. Open the download once on your submission device before retrying the portal.
Generic resize instead of 1200×628 page?
Generic resize works broadly, this page names the exact box so search intent matches the checklist. Neighboring tools exist for nearby sizes; switching is better than forcing the wrong ceiling.