Craft · 6 min read · May 2026
Designing in Tamil and English together
The usual sequence is to design in English, approve it, and then ask for the Tamil version. That request looks small and is not, because the two scripts do not occupy space the same way.
Almost every business in Chennai eventually needs both. A signboard, a menu, a government tender document, a flyer going to a mixed neighbourhood. The work goes smoothly when both languages are in the brief on day one and badly when Tamil arrives after the layout is locked.
Four things that differ
None of these are opinions. They are properties of the script that a layout either accommodates or fights.
01
Tamil runs longer
The same sentence typically takes 20 to 30% more space. A headline that fits two lines in English will not fit two lines in Tamil at the same size.
02
It needs more vertical room
Tamil has marks above and below the baseline. Line spacing set tight for English makes those marks collide, which is how bilingual menus become hard to read.
03
Font pairs are limited
Far fewer Tamil families exist than Latin ones, and fewer still have matching weights. Choosing the Tamil font first and pairing English to it works better than the reverse.
04
Small sizes fail sooner
Tamil loses legibility below about 9pt in print, where English survives to 7pt. This matters most on business cards and product labels.
What goes wrong when Tamil is added last
The English layout has a headline sized to fill two lines exactly, a button wide enough for the label, a panel tall enough for the paragraph. Tamil arrives thirty per cent longer and taller, and every one of those measurements is now wrong.
The temptation is to shrink the Tamil until it fits. This is the single most common failure I see, and it is visible instantly — the Tamil reads as a footnote to the English rather than an equal, which is the opposite of what a bilingual signboard is meant to communicate.
Shrinking the Tamil to fit tells every Tamil reader which language you consider the real one.
How to plan for both
Set the Tamil font first
Then pick a Latin family that matches its weight and proportions. Doing it the other way round means compromising the script with fewer options.
Size the layout for the longer language
Build the text areas around the Tamil, and English will always fit comfortably inside them. This costs nothing at the design stage and saves the whole layout later.
Match visual weight, not point size
The same point size can look lighter in one script than the other. Adjust until they read as equals, which sometimes means different numbers.
Decide the hierarchy deliberately
Which language sits on top, and does that change by location? A T. Nagar shopfront and an OMR office may want opposite answers. Choose rather than defaulting.
Get a native speaker to proof it
Not the translator — a second pair of eyes, reading it in place. Typesetting errors in Tamil are invisible to anyone who does not read it fluently.
On the translation itself
Machine translation is fine for understanding a sentence and unusable for anything printed. It produces Tamil that is technically correct and reads as though nobody who speaks the language checked it — which, on a signboard outside your shop, costs you more credibility than having no Tamil at all.
Marketing copy in particular does not translate. It gets rewritten. A tagline that works in English usually needs a different idea in Tamil, not the same idea in different words, and that is a writer's job rather than a designer's. I will always tell you when a line needs rewriting rather than converting.
One more thing worth checking before print: proper nouns. Business names, place names and people's names are where Tamil typesetting most often goes wrong, and they are also the words your customers will notice first.
Related reading
Need it in both languages?
Say so at the start and it costs considerably less than adding Tamil to a finished layout. A second-language edition planned from day one is roughly 60% of the original design fee.