Per-client 1200×630 Open Graph cards with locked brand colors and reusable templates — so every blog post, campaign, and press release ships with a share image that actually looks like the client's brand.
Open the Generator →A mid-size marketing agency with 10 active clients ships somewhere between 40 and 80 link-preview cards per month. Five blog posts per client, plus product launches, gated assets, press releases, and the occasional executive thought-leadership piece. None of them are individually important enough to justify opening Figma and pulling down the client's brand kit. All of them are collectively important enough that letting platforms auto-crop a stock photo into the link slot looks careless to the client's stakeholders.
That's the gap this generator fills. It's not for the hero campaign concept — Figma still wins there. It's for the long tail of weekly content where the design decision is already made (the client's brand template) and the only variable is the headline.
Every blog post the agency ships for a client needs an Open Graph image. Without one, the platform falls back to a cropped hero photo or, worse, the client's favicon at thumbnail size. Build one template per client — locked colors, locked logo position, locked typeface — and the only per-post work is pasting the headline. Account managers and junior strategists can ship cards without designer review.
When a client launches a multi-channel campaign with its own microsite or landing-page hub, the campaign needs a dedicated OG image distinct from the regular brand template. Generate the campaign card once, drop it into the landing page's og:image meta tag, and every share — paid social, organic posts, internal Slack threads, the press release — pulls the same on-brand preview. Cohesion across channels is what makes the launch feel like a launch.
PR pickups are where careless OG images cost the agency real money. A journalist tweets the client's press release link, the preview shows a stock newsroom thumbnail or a generic logo, and a sharable moment becomes a forgettable one. A press-release OG card with the headline and a clean client lockup looks deliberate — and trade publications increasingly pull the OG image straight into their own coverage as the article hero.
Whitepapers, industry reports, and benchmark surveys are the agency's bread-and-butter pipeline plays. The gated landing page needs an OG card that signals quality — title in display type, a one-line value prop, the client's accent color. This is the difference between a paid LinkedIn promotion that converts and one that gets scrolled past because the preview looks like clipart.
When a new-business team sends a proposal link to a prospect, the link previews in email and Slack. A generic preview signals "we use a generic template for new business." A custom card with the prospect's company name and a campaign concept teaser signals the agency has already done the thinking. Five minutes of effort that lifts the win rate noticeably on enterprise pitches.
The output is an unwatermarked 1200×630 PNG. There is no TinyTools logo embedded, no attribution required in the file, and no agreement to sign before exporting. Agencies can hand the file directly to the client, upload it through the client's CMS, or include it in a delivery zip alongside the rest of the campaign assets. The tool sits in the same category as TinyPNG for compression or RealFaviconGenerator for favicons — a focused utility you use, ship the output, and close the tab.
Because rendering happens client-side, no logo, headshot, or product photo you load into the canvas is ever uploaded to a server. That matters for agencies under embargo on unannounced product launches, M&A announcements, or financial communications. Open the browser dev tools network tab while you generate — there are no outbound requests for image data.
The pattern that works for agencies of 5 to 50 people: keep a per-client one-pager in Notion or Google Docs with four things — the locked hex codes (primary, secondary, accent), the logo position rule, the headline typeface (or the closest web-safe fallback if the brand font isn't free), and one example card the creative director has signed off on. When any account manager opens the generator for that client, they paste in the hex codes, position the logo per the rule, and the output matches the signed-off example. No designer in the loop for routine cards.
For agencies with formal brand guidelines from the client, this template doc is also the place to note the specific safe zones — the corners reserved for the client's logo, the minimum size for the wordmark, any required tagline placement. Most client brand guides assume print or hero layouts and don't speak to OG specifically. The agency adds that interpretation once per client, then everyone follows it.
og:image meta tag points to the absolute URL of the new file, not a relative path?v=2026-05 cache-buster to the image URL if you're re-uploading to the same pathYes. Templates are defined by the hex codes, logo position, and typography rules in the per-client one-pager — not by an account login. Any team member who opens the generator can recreate the client's locked template by pasting the same values. This is intentional: it removes the bottleneck of one designer owning every brand file.
For Fortune 500 clients with formal brand-compliance review, treat the generator output the same as any other agency deliverable — route the first card per template through the client's brand team for sign-off, then reuse that approved template for the long tail. The output is a flat PNG, so it goes through whatever compliance pipeline the client already runs for static assets.
For hero campaign concepts, brand-system work, and anything that requires actual design judgment — yes, absolutely. This generator handles the routine, high-volume share cards that don't require a designer's eye on each one. Most agencies find their designers prefer this split: more time on the work that uses their craft, less time exporting a thousand 1200×630 PNGs from a Figma frame.