OG image generator

What this OG image generator makes

An Open Graph image is the artwork a page can name in its social metadata. This generator combines one local image with a title, eyebrow and site label on a real raster canvas. You can cover the artwork panel and choose the crop focus, or contain the complete source over an explicit background. The visible canvas and both downloads use the same layout function; there is no separate thumbnail template that can quietly drift from the exported pixels.

The output is a PNG and a JPEG at the exact whole-pixel dimensions entered in the controls. The browser opens both encoded blobs again and confirms their width and height before the download links appear. PNG is useful when crisp flat color matters. JPEG is usually smaller for photographic artwork and always has an opaque background. Neither file contains the source camera metadata, editing history or animation. A GIF or animated WebP contributes the still frame that this browser decodes for the canvas.

An exact asset preview is not a social feed simulator

The preview is exact about the file CreatorValet can control: its canvas, crop, padding, colors and text in this tab. It is not a promise about Facebook, LinkedIn, X, Slack or a messaging app. Those products can choose a different metadata image, refresh a cached card later, crop a display slot, add padding or change their interface without changing your exported bytes. This tool does not fetch a page URL, publish the image or imitate platform chrome, so it cannot honestly claim to show exactly how a future post will appear.

That boundary also separates generation from checking. A URL-based Open Graph checker must retrieve published HTML, follow its metadata and report what was actually reachable. This generator has no remote fetch and no hosting step. After downloading, place the image at a stable public URL and add the appropriate metadata in your own site. The website image extractor can inventory the image declarations visible in HTML you already have, but it does not certify a social platform's cache or selection.

Open Graph does not mandate one timeless image size

The Open Graph protocol requires a title, type, image URL and canonical URL for a basic object. It also defines optional structured image properties for secure URL, MIME type, width, height and alternative text. It does not state that every Open Graph image must be 1200 by 630 pixels. That familiar canvas can remain a useful custom starting point, but presenting it as a protocol law would turn common practice into a false standard.

Platform shortcuts are therefore stored as a dated registry rather than hidden constants. The only platform preset currently exposed is LinkedIn's custom Page URL preview. LinkedIn's own help page, checked August 12, 2026, describes a 1.91:1 ratio and recommends 1200 by 627 pixels for that particular surface. The preset names the surface, links the source and shows the verification date beside the selector. It does not claim to cover ordinary feed photos, profile images, banners, ads or another platform. Custom width and height remain available at all times.

Cover, contain, padding and focus are separate choices

Cover scales the source until the complete artwork panel is filled. A wide photograph in a tall panel loses pixels from its sides; a tall photograph loses pixels from its top and bottom. Horizontal and vertical focus decide which side survives instead of assuming the subject is centered. Contain scales until the complete source fits, so the selected artwork field can remain visible around it. Neither mode changes the source aspect ratio or stretches a face, logo or screenshot.

Padding shrinks the drawable panel by the stated percentage on each side before the fit is calculated. It is not an invisible safe-zone claim. A real platform can overlay text or crop differently in a context this local page cannot inspect. Use padding as a deliberate design margin, and keep critical words or faces away from the source edges when the destination is uncertain. For a pure resize or a batch of existing finished images, the bulk image resizer is the narrower tool: it applies exact pixel rules without adding this title layout.

Fonts and Unicode have a visible boundary

The title uses the site's self-hosted display face and the smaller labels use its self-hosted sans-serif face. Those files are served with the page rather than requested from a font service. When a title contains a glyph those bundled faces do not include, the browser selects a local fallback. Preview and export in the same tab use that same resolved font, but a second device can own a different fallback and shape an emoji, CJK character or uncommon symbol differently. The tool flags extended text instead of claiming byte-identical typography across operating systems.

Long titles are wrapped to at most three lines and can be shortened with an ellipsis when the canvas cannot contain more. The renderer iterates Unicode code points when it must split an unbroken token, so it does not cut a surrogate pair in half. The best result still comes from editing the headline until the full wording appears in the preview. An OG image should support the page title, not become the only place where essential information exists.

The artwork and generated bytes stay local

Choosing, dropping or pasting an image gives this tab a local File object. The browser decodes those bytes, draws the canvas and creates temporary blob URLs for download. There is no image upload endpoint, AI call, URL fetch, remote font, account or hosting operation in the flow. Large images can still consume substantial tab memory, so the shared size advice appears before decoding and lets you continue rather than rejecting a file merely because it is large.

The receipt reports the dimensions obtained by reopening both exported blobs. You can also inspect the Network panel while generating; selecting the image should not create a request carrying its bytes. The local-processing verification guide explains that check and its limits. If the final PNG is larger than a publishing system accepts, use the image compressor on the downloaded file as a separate, measurable step instead of hiding quality loss inside this generator.