Files stay on your device. Enter send · Esc close drawers
1920×1005 JPEG · ~1.91:1
Design assets often have to ship at a single canonical size — an icon set, a profile picture, a thumbnail — because platforms or frameworks will reject anything off-spec. Facebook Event Cover produces 1920×1005 JPEG, the size Facebook Event Cover expects.
| Output dimensions | 1920×1005 pixels |
|---|---|
| Aspect ratio | 1920:1005 (1920:1005) |
| Output format | JPEG @ 92% quality |
| Processing | 100% in your browser — no upload |
| Cost | Free, unlimited |
| Source | Official guidelines |
Audience: 3+ billion accounts, the most demographically broad platform.
How Facebook ranks images: feed ranking heavy on Meaningful Social Interaction signals — comments, replies, family connections. Posting at the platform's exact native dimensions (1920×1005 px) preserves your original framing and avoids the softening that happens when the platform's own resampler runs to fit its expected size.
Platform-specific note: Facebook compresses images server-side when uploaded over mobile data; uploading at native size from desktop avoids the worst of this.
This preset is a deterministic recipe — every step has fixed parameters so the result is byte-identical across runs of the same input.
Facebook Event Cover crops your input to 1920:1005 and resizes it to 1920×1005 px as JPEG — a 1.9-megapixel output. The work runs through canvas APIs and a WebAssembly image-encoder; the source image is decoded into an off-screen canvas, transformed in place, and re-encoded without any network upload.
Design deliverables to clients often require an exact pixel-size; this preset's deterministic output makes the deliverable repeatable. The browser-side path also means the file never leaves your device — relevant when the input contains personally identifiable information, screenshots of private documents, ID scans, or proprietary product photography.
1920×1005 px, saved as JPEG at quality 92%.
The target platform — see the cited spec — uses 1920:1005 as its native frame. Submitting any other ratio means the platform's own crop runs, which often clips faces or text near the edge.
The target accepts JPEG, and JPEG compresses photographic content 5-10× smaller than PNG with no visible difference at quality 92%. PNG is the right choice only when the image has hard edges or transparency — which photo-ID, social posts, and product photos don't.
No. This preset runs entirely in your browser using WebAssembly + canvas APIs — no server round-trip. You can verify this in your browser's network panel: only static asset requests, no image upload. The file never leaves your device.