Designing a Bilingual Seal: Two Scripts, One Ring, Not Much Room

The request usually arrives from someone outside the company. A freight forwarder asks whether the stamp on the bill of lading names the shipper. A European client's legal team sends back a signed contract with a polite note: we cannot read the seal, could you confirm the entity? An overseas bank wants documentation that ties the red circle to the name on the invoice.

None of these are objections to the seal. They are objections to being unable to read it. And the instinctive fix — add the English name — is where the design problem starts, because a seal ring is a fixed amount of space and a company name in two languages is roughly two company names.

This is a piece about that squeeze. What actually fits, what to cut, where each script goes, and the point at which the honest answer is "don't put both on one seal."

First: do you need one bilingual seal or two seals?

Worth pausing here, because the second option is often better and almost nobody considers it.

A single bilingual seal makes sense when the same document has to satisfy readers in both languages at once — an export contract signed by a Chinese supplier and a German buyer, a certificate of origin, shipping paperwork that passes through several hands. One impression, two audiences, no ambiguity about whether the two seals belong to the same company.

Two separate seals make sense when the audiences don't overlap. Domestic paperwork gets the local-script seal, exactly as everyone in that market expects it. Foreign-facing paperwork gets a seal designed for foreign readers. Each one gets the full ring to itself and is legible without compromise. The cost is that you now have two marks to manage, and a counterparty who sees both may reasonably wonder which is the real one — a question you should be able to answer in writing before you create the second seal. Why one company ends up with five seals covers how to keep a set like that coherent.

There is also a third option people skip past: leave the seal alone and solve the problem in the document. A line of text under the signature block — Seal of ABC Import & Export Co., Ltd. (示例进出口贸易有限公司) — answers the reader's question completely and costs nothing in ring space. If the only complaint is legibility, this may be all you need.

Whether a bilingual seal is required anywhere is a separate question, and the answer is jurisdiction-specific rather than general. Read the country pieces — electronic seals in China, hanko and electronic seals in Japan, dojang and electronic seals in Korea — and check with whoever handles your registrations before you assume a bilingual ring is either allowed or expected in your case.

The geometry: why the second language is always the problem

Here is the thing that makes bilingual seals hard, and it is not aesthetic.

CJK characters are square, dense, and semantically heavy. A Chinese company name might be eleven characters — 示例进出口贸易有限公司 — and those eleven characters sit comfortably around the top arc of a 40mm circle at a size you can read.

The English equivalent, DEMO IMPORT & EXPORT CO., LTD., is thirty characters. Same arc, nearly three times the glyph count, and each Latin letter carries a fraction of the meaning a Chinese character does. To fit it in the same space, you shrink it. Shrink it enough and it becomes a gray texture that says "there is English here" without being readable — which is worse than useless, because it consumed space and solved nothing.

So the real design constraint is: the second-language line must stay above its own legibility floor, or it should not be there. Everything below follows from that.

Where each line goes

The layout that has settled into common use, and the one the bilingual seal template starts from, looks like this:

Top arc: the registered name in the local script. This is the primary identification and it gets the best position and the most space.
Bottom arc or lower sub-line: the second language — an English name or a purpose descriptor.
Center: a star, an emblem, or nothing. Whatever the local convention already uses.

Keep the hierarchy honest. The registered name is the thing that identifies the entity; the translation is support. Giving them equal visual weight makes the seal look like it belongs to two different companies, and it eats the space the registered name needs.

If the seal also needs a purpose line — 合同专用章, FOR INTERNATIONAL BUSINESS — you now have three text elements competing for two arcs and a center. That is usually one element too many. Drop something, or accept that this seal is doing too many jobs and split it. The anatomy of a single-language seal is covered in how to design a company seal; the bilingual version is the same anatomy with less room.

Shortening the second line without saying something untrue

This is the part that requires judgment rather than technique, and it is where I would be most careful.

If your company has a registered English name, use it exactly. Not a cleaned-up version, not an abbreviation you invented for the ring. If the registration says "CO., LTD." then that is part of the name. Trimming it to make the arc fit changes what the seal claims about the entity, and a counterparty's compliance team may notice the mismatch against your business licence long before they notice the typography.

If your company does not have a registered English name, then whatever you put on the bottom arc is a descriptor, not a name — and it should read like one. Something like FOR INTERNATIONAL BUSINESS or EXPORT DOCUMENTS is a description of what the seal is for. A plausible-looking English trading name that appears on no registration document is an invitation to a question you don't want.

Honest ways to buy space:

Use the registered short form if one exists on the registration.
Drop the descriptor line and keep only the name, or vice versa — rarely do you need both.
Move the second language to a straight line across the lower half instead of an arc. Straight text reads better at small sizes than curved text and often fits more.
Use a larger seal. If the ring is genuinely too small for what has to go on it, 40mm was the wrong starting number. Seal size and resolution covers how to think about physical size and pixels together.

Dishonest ways that will tempt you: inventing an English name, abbreviating the entity type in a way the registration doesn't, or shrinking the second line to 6pt and calling it done.

Typography: you are always using two typefaces

There is no single font that renders a Chinese company name and a line of English capitals equally well. Even fonts with wide coverage handle the two scripts with different design intent, and a seal magnifies the mismatch because the text is small, curved, and printed in one flat color.

The practical approach is to set each script in a typeface built for it — the generator ships Noto Serif SC / TC / JP / KR alongside Latin serifs for exactly this reason — and then tune for optical weight rather than point size. A CJK serif at 20px and a Latin serif at 20px will not look like they belong together. The Latin will usually look lighter and longer. Expect to set the Latin line smaller in absolute terms and still have it read as equally present. The seal fonts guide goes deeper on script mixing and why fallback fonts quietly ruin seals.

Two more typographic notes that matter more on a ring than anywhere else:

Use capitals for Latin text on an arc. Lowercase letters have ascenders and descenders that fan out unevenly when text follows a curve, and the descenders collide with the ring line. Capitals sit on a single baseline and curve cleanly. This is why nearly every bilingual seal you have seen uses all-caps English — it is not a stylistic convention, it is a consequence of the geometry.

Watch letter-spacing on the curve. Text on a tight arc needs a little extra tracking to stop the inner edges of letters from crowding. Too much and the line stops reading as words. This is a by-eye adjustment; there is no correct number.

Scripts that don't behave like Latin

If the second language is Arabic, Thai, Devanagari, or another connected or complex script, most of the advice above stops applying and I would be cautious about a curved bilingual layout at all.

Arabic is connected and right-to-left: adding letter-spacing to fit an arc breaks the joins between letters, which is not a stylistic issue but a correctness one. Thai stacks marks above and below the baseline, which a tight ring will clip. Devanagari hangs from a headline that a curve distorts.

The workable answer for these is usually a straight line rather than an arc, more vertical room, and — if the design is going anywhere official — review by someone who reads the script. A seal with mangled Arabic is more damaging to your credibility with an Arabic-reading counterparty than a seal with no Arabic at all.

Test it the way it will actually be seen

A bilingual seal that looks fine at 800px in a design view is not evidence of anything. The failure mode is specific and predictable: the second-language line survives on screen and dies on paper.

Before you commit to a design:

Render it at the size it will occupy on a real page — often 15–25mm across, much smaller than it looks while you are editing.
Print it in black and white. Color helps separate a seal from text; grayscale removes that help, and the color and contrast guide explains what survives the conversion.
Scan or photograph the print and look at it again. This is the state most counterparties will actually receive.
Show it to someone who reads only the second language and ask them to read the line aloud. Not "can you see it" — read it.
Place it over real document text, not empty white space. A transparent PNG over a dense paragraph is a harsher test than a clean background; how to create a transparent PNG seal covers producing one properly.

If the second line fails steps 3 or 4, it is decoration. Cut it, enlarge it, or move it to a straight line — but don't ship it.

A short checklist

The registered local-script name is the dominant element.
The second language is either an exact registered name or an obvious descriptor.
Nothing on the ring implies a legal name that doesn't exist on a registration document.
Each script uses a typeface designed for it, matched by optical weight rather than point size.
Latin text on arcs is set in capitals.
The second-language line is readable in a black-and-white scan at real page size.
The seal has one job; purpose lines and translations are not both crammed onto the same ring.
You know which documents get this seal and which get the local-script one.

A bilingual seal is a compromise by definition — you are asking one 40mm circle to do a job that was designed for one language. Done well, it answers a foreign reader's question before they have to ask it. Done badly, it adds an illegible gray band and a new thing to explain.

Start from the bilingual layout template, or build from scratch in the online seal generator and browse the template gallery for the single-language layouts if you decide two seals serve you better than one. And before you rely on any generated image in a real workflow, are image seals legally valid? is worth ten minutes.