ogmake

Guide

Make a free Open Graph image locally

Drop a link into chat, social, or a doc, and platforms often pull a preview image. Without a default, they may grab a blank, a random crop, or nothing—weak first impression.

Ogmake generates a title/brand-style Open Graph share image locally. Free to export. Per product positioning, the design flow is not built as “must upload artwork to our servers for cloud render.”

1. What an OG image is

Open Graph–related tags tell a platform: “when this URL is shared, use this image and this title.” Before anyone clicks, they see the preview.

This page focuses on making the image. Field-by-field tag minutiae vary by platform and change over time—verify current docs when you wire meta tags.

For indie tool sites, the OG image is often the only brand surface a stranger sees in Slack or X before they decide to click. Treat it like a tiny billboard, not an afterthought PNG.

2. Why sites need a default share image

Tool sites, blogs, and docs without a share image get ugly or unpredictable previews. One fixed default at least puts your name and main line on the card.

You do not need a designer per article on day one. Ship a “not embarrassing” default, then iterate.

Homepages, pricing, and docs entries that share one clear default card look more intentional when people paste links in group chats.

Changelog links and “we shipped X” posts especially need a default. Without one, your launch URL looks unfinished next to competitors who bothered to set a card.

3. Generate with Ogmake

Open Ogmake, enter title and brand-facing copy, generate the card, export.

Fits: sitewide defaults, consistent article list cards, a hangable image before launch. Complex illustration systems still belong in a design tool. Ogmake’s job is a usable default share image. Support: [email protected].

Write human copy: what you do in one line beats a pile of adjectives. Keep type large enough to read in a small chat thumbnail.

Safe margins matter more than perfect kerning. Titles glued to the edge get cropped in some clients. See social card image sizes.

4. Size: ~1200×630 as illustration—not eternal law

Many tutorials cite about 1200×630 as a starting point. That is an illustrative / common starting size, not eternal law and not a statute.

Platforms (social, messengers, doc previews) change crops and recommendations. Before you finalize, check each platform’s latest public docs. Leave safe margins so edge titles survive crops.

This guide does not invent official Meta/X pixel tables. Outdated blog “must be N×M” posts are clues only. Official docs plus a real preview win.

5. After export: stable HTTPS URL + OG tags

Host the image on your site or object storage. Point page meta (OG image, plus title/description as needed) at a stable HTTPS URL.

Exact CMS click-paths differ by stack. This page does not invent unverified admin menus. Principle: stable URL, correct protocol, think through filename or cache when you replace the file. Then use each platform’s debug/fetch tool and expect cache delay after swaps.

If you overwrite the same path, old previews may linger. Sometimes a new filename is the boring reliable fix. Details on defaults for blogs/tool sites: default social share image.

6. Split: Ogmake for cards; Heiclocal/Metastrip/Stampdrop for real photos

Do not merge “strip EXIF on a portrait” and “make an OG card” into one confused step. Different assets, different folders.

FAQ

Upload?
Local generation per product positioning—not a flow that requires uploading source art to our servers.

Must it be 1200×630?
Common start only. Check platform docs.

Replace Figma / Pseudo?
Fine for defaults; complex brand systems may still need a design suite.

X / Twitter cards?
Make the image here; wire tags per current platform docs.

Related reading

Disclaimer

Ogmake is not a Meta / X / LinkedIn official tool. Previews follow each platform’s fetch and cache. Support: [email protected].