Design Japanese Open Graph Cards With AI
Most templates squash Japanese type — half-width punctuation, kana that collapses, headlines that lose all breathing room. Oginify treats 日本語 as first-class so every card feels editorial.
Why Choose Oginify
Real Noto Sans JP + Serif JP
Every card ships with genuine Noto Sans JP and Noto Serif JP subsetted per page — not a Western fallback that turns kanji into tofu boxes or half-width forms.
Correct Japanese punctuation
Full-width 、and 。 stay full-width; ・ middle dots preserved; ellipsis stays as ⋯; Latin words inside Japanese sentences pick up the right thin space around them.
Mixed kana + kanji + Latin
Brand names like Oginify, GitHub or React sit next to 日本語 headlines without breaking the baseline — kanji, hiragana and Latin runs share one visual grid.
Survives LINE and Zenn crops
LINE previews crop cards aggressively and Zenn re-renders them at small sizes. The Japanese preset uses oversized display type and one seal-stamp accent so the headline still reads at thumbnail size.
Vertical 縦組み aware
Layouts respect the classical top-to-bottom reading rhythm even in horizontal cards — dates and small labels sit where a Japanese editor expects, not where a Western template guessed.
Tuned for note, Zenn and Qiita
Ready-made presets for note magazine masthead, Zenn dev-post covers and Qiita article cards — each with the right density, hairline rules and one-color accent.
SaaS · Landing page
Japanese SaaS landing — しずかSaaS
Japanese SaaS pages built from translated English templates squash headlines, drop half-width punctuation and let CTAs shout. Oginify rebuilds the layout in real Noto Sans JP and Noto Serif JP so the three tiers — display, subhead, CTA — each breathe.
Editorial · Long-form newsletter
Japanese newsletter — 拾光通信
note covers are 1280×670 and LINE crops them further — a single-line headline can vanish. This layout uses oversized Noto Serif JP for the masthead, italic Serif JP for the subhead and a single vermillion seal-stamp so the card still reads at fingernail size.
E-commerce · Seasonal drop
Japanese DTC — しずか商店 summer linen
Japanese e-commerce cards shared on Rakuten, Instagram and LINE Official swallow full-width punctuation, flip prices into Latin faces and warp product photos. Oginify switches to tabular numerals, preserves full-width marks and crops the shot to the 1200×630 golden ratio.
Devtool · Japanese docs
Japanese dev docs — コードの炉
The classic failure on Japanese devtool sites is a monospace face that half-width-crushes kanji while comments fall back to Mincho. This layout assigns Noto Sans JP to Japanese comments and JetBrains Mono to code, keeping baselines aligned across the mixed run.
The Prompts Behind These Four Examples
Each example above started as a one-paragraph prompt. Here are the four we used — paste them into Oginify with your own URL and you'll get the same direction in your brand.
SaaS · しずかSaaS / Landing
Generate a 1200×630 Open Graph card for a Japanese B2B SaaS landing page called しずかSaaS. Warm off-white background, small vermillion mono Noto Sans JP label top-left reading しずかSaaS / ランディング. Left: large deep-charcoal Noto Sans JP headline チームの仕事を、もっと静かに, smaller muted Noto Serif JP subline beneath 日本のチームに最適化した B2B コラボレーション. Right: quiet faded UI fragment of a Japanese dashboard with sidebar navigation. Editorial minimal, generous negative space, sharp corners, one vermillion accent, no shadow.
Editorial · 拾光通信 / Issue 27
Generate a 1200×630 Open Graph card for a Japanese long-form newsletter called 拾光通信, issue 27. Off-white paper background with faint texture. Classical Noto Serif JP masthead centered top reading 拾光通信 with thin hairline rules above and below, and a small vermillion mono date stamp on the right edge of the lower rule reading 第 27 号 · 2026 年 7 月. Centered below: tall Noto Serif JP headline 情報の洪流のなかで、ふたたび読むこと, italic Noto Serif JP subline 手を止めて、長い文章に戻る手紙. Black ink only plus one small vermillion stamp.
E-commerce · しずか商店 / Summer
Generate a 1200×630 Open Graph card for a Japanese DTC e-commerce campaign called しずか商店. Warm off-white background. Left: bold Noto Sans JP headline 夏の新作 · 麻シリーズ in deep charcoal, italic Noto Serif JP subhead beneath 北ポルトガル産の手織りリネン. Small vermillion Noto Sans JP label top-left しずか商店 / 新入荷. Right: soft-focus photographic scrap of folded oatmeal linen on light wood, torn paper edge. Editorial and quiet, one vermillion accent only, sharp corners, no shadow.
Devtool · コードの炉 / Japanese docs
Generate a 1200×630 Open Graph card for a Japanese developer-tool docs page called コードの炉. Warm paper cream background. Top-left small vermillion Noto Sans JP mono label コードの炉 / 日本語ドキュメント. Left: large deep-charcoal Noto Sans JP headline より速いビルド、より安定したデプロイ, subhead in JetBrains-Mono-style beneath 新しい CI エンジン · インクリメンタルキャッシュ対応. Right: quiet faded terminal fragment showing Japanese comments alongside code snippets, torn paper edge. Premium B2B devtool aesthetic, generous negative space, one vermillion accent, sharp corners.
Frequently Asked Questions
What Japanese fonts does Oginify use, and are they free for commercial use?
Noto Sans JP and Noto Serif JP — both released by Google + Adobe under the SIL Open Font License, free for commercial use. We subset per page so the card renders even when the reader's device has no Japanese font installed.
How large should a Japanese headline be on a 1200×630 OG card?
36–52px equivalent — noticeably larger than the same headline in English. Kanji carry more visual weight per glyph and downsample poorly on LINE and Zenn thumbnails. The Japanese preset defaults to 46px display for the main headline.
Does the card unfurl correctly on LINE, X (Twitter), Zenn and note?
Yes on X, Zenn and note — they all read og:image and og:title from the page head. LINE reads them too when the URL is shared into a chat. For LINE Official Account rich messages you upload the 1200×630 PNG directly; Oginify exports the same file.
How does Oginify handle mixed Japanese and English inside one headline?
Write the headline as you'd type it — 「Oginify で OG 画像を生成」. The renderer detects CJK vs Latin runs and applies Noto Sans JP or Inter per run, so kanji, kana and Latin share one baseline without the usual half-width collapse.
Can I use vertical 縦書き layouts on the card?
The 1200×630 canvas is horizontal, so full vertical typesetting isn't the goal — but the Japanese presets keep the editorial rhythm of 縦組み (date stamps, side labels, hairline framing) so the card still reads as Japanese, not translated Western.
Do you support half-width katakana and legacy encodings?
The renderer uses full-width kana by default and preserves half-width only when the source URL uses it. Legacy Shift-JIS pages are fetched, normalized to UTF-8, and rendered correctly — no mojibake in the output card.
Ship Japanese Open Graph cards that read like editorial, not translation.
Paste any Japanese URL — real Noto Sans JP / Serif JP, correct punctuation, one seal-stamp accent, and 1200×630 output in seconds.