Tamil font Encoding Guide (2026)

Tamil font encoding explained simply — what ANSI fonts are, why TSCII failed, how Unicode solved everything. Beginner-friendly comparison with conversion steps included.

What is Character Encoding? A Simple Explanation

Tamil font encoding sounds technical, but the concept is surprisingly simple. Every time Tamil text has broken on your phone, or a document someone sent you showed up as gibberish instead of Tamil — that was an encoding mismatch. Once you understand this concept, you will know exactly where the problem is and how to fix it.

Every character you see on a computer screen — whether it is the letter “A” or the Tamil letter “க” — is stored internally as a number. Character encoding is the rulebook that defines which number represents which character.

🔒 Think of It This Way

Imagine a locker room where every locker has a number. For English, the rulebook says Locker 65 contains “A”, Locker 66 contains “B”, and so on. This system is called ASCII, and it provides 128 lockers — plenty for 26 English letters plus digits and punctuation. But Tamil has 247 characters (12 vowels + 18 consonants + 216 combinations + Aytham ஃ). The 128 lockers of ASCII are nowhere near enough. So people invented different strategies to create more lockers — and those different strategies became the different Tamil encoding systems. Learn more about the full history of Tamil fonts.

📅 Tamil Encoding Timeline at a Glance

1990s-2000s
ANSI Era: Bamini, SaiIndira, Vanavil — every developer created their own incompatible system. Chaos.
Late 1990s
TSCII Emerged: First unified Tamil standard. Solved compatibility between TSCII fonts but was Tamil-only.
1991
Unicode 1.0: Tamil included from the very first version with 61 characters. Global standard begins.
2001-2003
Windows Support: Microsoft included Latha Tamil font in Windows XP. Mainstream adoption begins.
2008
Unicode 5.1: Tamil block expanded to current 72 code points. Standard finalized.
2010s-2026
Universal Adoption: WhatsApp, Instagram, Facebook, iOS, Android all standardize on Unicode. Legacy encodings become obsolete.

❶ ANSI Encoding — The Bamini and SaiIndira Era

1990s – 2000s · Multiple incompatible systems · Now legacy status

How ANSI Tamil Fonts Work

In the 1990s, developers found that beyond the standard 128 ASCII lockers, there were 128 more extended lockers available (positions 128-255). They placed Tamil characters in these extra lockers. The problem was that every developer independently decided which Tamil character went into which locker — with no coordination whatsoever.

MechanismFont file displays Tamil shapes over English character positions
What’s actually savedEnglish letters — Tamil is just a visual mask
Remove the font?Text breaks into English gibberish

Major ANSI Tamil Fonts

  • Bamini — the most widely used, dominant in Sri Lanka and Tamil diaspora communities (Canada, UK, Australia, Europe)
  • SaiIndira — popular in Tamil Nadu government offices and educational institutions
  • Vanavil Avvaiyar — adopted by the Tamil publishing and media industry
  • Amudham, TAB, Shree Tamil — used by various organizations in different regions

The Fatal Flaw

⚠️ In Bamini, pressing “j” produces “க”. In SaiIndira, pressing “j” might produce an entirely different Tamil character. No two ANSI fonts are compatible with each other. And none of them work on WhatsApp, Instagram, mobile phones, or any platform that does not have the specific font file installed. For a detailed breakdown, read our Bamini vs Unicode comparison.

❷ TSCII — A Good Idea That Ran Out of Time

Late 1990s – mid 2000s · Community-driven standard · Overtaken by Unicode

What TSCII Was Trying to Do

A group of Tamil computing enthusiasts saw the chaos caused by dozens of incompatible ANSI fonts and proposed a solution — one fixed, publicly documented, open standard that every Tamil font could follow. This was TSCII — Tamil Script Code for Information Interchange.

Key difference from ANSIOne official character mapping — all TSCII fonts are compatible with each other
How it fit 247 charactersMulti-byte encoding — some characters use 2 bytes instead of 1
Fonts built for TSCIITSCu_Times, TSCu_Comic, TSCu_Paranar

Why TSCII Did Not Survive

⏳ TSCII was a Tamil-specific solution operating within the ASCII framework. When the global computing industry adopted Unicode — which covers every language on earth — TSCII became incompatible with modern platforms. WhatsApp, browsers, phones — everything moved to Unicode. TSCII is effectively obsolete in 2026.

❸ Unicode — The System That Changed Everything ✨

1991 (defined) – Present · International standard · Powers the entire modern web

What Makes Unicode Different

Unicode is a global character encoding standard maintained by the Unicode Consortium, whose members include Apple, Google, Microsoft, IBM, and Adobe. While ASCII offers 128 lockers and extended ASCII offers 256, Unicode provides space for over 1.1 million characters — enough to cover every writing system on earth. Tamil does not need clever workarounds or extra lockers — it has its own properly reserved space.

Tamil’s reserved blockU+0B80 – U+0BFF (72 code points assigned)
First includedUnicode 1.0 in 1991 (61 characters initially)
Current state72 code points stable since Unicode 5.1 (2008)

A common question: How do 72 code points represent all 247 Tamil characters? The answer is that Unicode uses a combining system. The 216 consonant-vowel combinations are not stored as individual code points — instead, a base consonant (like க = U+0B95) combines with a vowel sign (like ா = U+0BBE) to produce “கா”. This is how 72 code points efficiently cover all 247 characters.

Why Unicode Solved the Tamil Encoding Problem

✅ Unicode separates character data from font styling. The code point U+0B95 always means “க” — on any device, any operating system, any font, any application. The font only controls how “க” looks visually (bold, thin, rounded, serif). The character identity itself never changes and never breaks.

Popular Unicode Tamil Fonts Today

Noto Sans Tamil (Google, pre-installed on Android), Latha and Nirmala UI (Microsoft, included in Windows), Mukta Malar, Catamaran, Baloo Thambi 2, Hind Madurai — all free and available at the Tamil Font Download page. For messaging apps, see our WhatsApp Tamil Font collection.

Side-by-Side Comparison of All Tamil Encoding Systems

ParameterANSI (Bamini etc.)TSCIIUnicode ✨
Standardized?❌ Every font different⚠️ One published spec✅ International standard
Cross-font compatible?❌ No⚠️ Within TSCII only✅ Universal
WhatsApp❌❌✅
Instagram❌❌✅
Mobile phones❌❌✅ All devices
Google indexable?❌❌✅ Fully
Screen readers / accessibility❌❌✅
Status in 2026Legacy — decliningObsolete✨ Current standard

How to Convert Legacy Tamil Encoding to Unicode

If you have old Tamil text in Bamini, SaiIndira, Vanavil, or TSCII format, converting it to Unicode takes about 30 seconds.

🔄 The Tamil Font Generator on TamilFontEmpire supports these conversions:

  • Bamini → Unicode
  • TSCII → Unicode
  • SaiIndira → Unicode
  • Vanavil → Unicode

Steps: Paste the legacy text → select the source encoding → hit convert → copy the clean Unicode output → use it anywhere.

📢 Help others understand Tamil encoding — share this guide:

💬 WhatsApp 🐦 Twitter 📘 Facebook ✈️ Telegram

How to Tell Which Encoding Your Tamil Text Uses

Before you can fix broken Tamil text, you need to know which encoding it is in. You do not need any software — the symptoms tell you almost immediately.

The 30-second test

Copy the text and paste it into a plain, font-neutral place: a browser address bar, a Google search box, a WhatsApp chat, or Google Docs. These use Unicode by default, so they strip away any custom font. Then look at what appears:

What you see after pastingWhat it meansWhat to do
Readable Tamil (அழகான தமிழ்)The text is already UnicodeNothing — it works everywhere
Random English letters & symbols (e.g. “mfhdhd mw;kh”)ANSI font encoding (Bamini, SaiIndira, Vanavil)Convert to Unicode
Boxes (□□□□) or question marks (????)Unicode text, but the device lacks a Tamil fontInstall a Tamil font / update the OS
Partly broken — some letters fine, some wrongUsually TSCII, or a mixed-encoding documentConvert to Unicode
✅ Rule of thumb: If the text only looks correct in one specific document or on one specific computer, and turns to gibberish everywhere else, it is a legacy font encoding (ANSI). Real Unicode looks the same everywhere.

Why ANSI text looks like English gibberish

Remember the “lockers” analogy. An ANSI Tamil font puts Tamil shapes into the lockers that normally hold English letters. So the file actually stores English letters — the Tamil appearance only exists while that one font is applied. Strip the font (which any modern app does) and you are left with the raw English letters that were stored underneath. That string of nonsense English is the tell-tale sign of ANSI encoding.

How to Type Unicode Tamil on Any Device

Once you know Unicode is the only encoding worth using, the next question is how to actually type it. Every major platform now ships with Tamil input built in — no third-party font needed.

Android

Gboard (Google’s keyboard, pre-installed on most phones) supports Tamil. Go to Settings → Languages & input → add Tamil. You can choose between a phonetic layout (type “amma” and it suggests அம்மா), the Tamil99 layout, or the handwriting option. Everything you type is Unicode.

iPhone / iPad

Go to Settings → General → Keyboard → Keyboards → Add New Keyboard → Tamil. iOS offers both the Tamil99 layout and a phonetic (transliteration) layout. Switch to it with the globe key while typing.

Windows

Go to Settings → Time & Language → Language & region → Add a language → Tamil (India). Windows installs the Nirmala UI font and gives you the Tamil99 and phonetic keyboards. Switch layouts with Windows key + Spacebar.

Mac

Go to System Settings → Keyboard → Text Input → Edit → add a Tamil input source (Tamil99 or Tamil phonetic). Switch with the input menu in the menu bar.

Typing on the web

If you are on a shared or older computer, Google Input Tools and similar online Tamil keyboards let you type phonetically in the browser and copy the Unicode output. For styling that text afterwards, run it through the Tamil Font Style Generator.

✅ Layout tip: If you are new to Tamil typing, start with the phonetic layout — you type the sound in English letters and it converts to Tamil. Once you type Tamil often, the Tamil99 layout is faster because it is designed specifically for the Tamil script.

Migrating a Legacy Tamil Website to Unicode (SEO Checklist)

If you run an older Tamil website built with Bamini, SaiIndira, or TSCII, there is a hidden cost: search engines cannot read a word of it. To Google, ANSI Tamil looks like meaningless English strings, so the pages never rank for Tamil queries. Migrating to Unicode is the single biggest SEO improvement such a site can make.

Why it matters for rankings

Google indexes the stored characters, not the visual appearance. A Bamini page that looks like perfect Tamil to a human is stored as gibberish English, so Google indexes gibberish. Converting the same content to Unicode lets Google finally read, index, and rank it in Tamil search results — often recovering traffic the site never knew it was losing.

Step-by-step migration checklist

  1. Audit your content. Identify which pages use legacy encoding (use the 30-second paste test above on a few pages).
  2. Convert the text. Run each block of legacy Tamil through a converter (Bamini/TSCII/SaiIndira → Unicode) and replace the old text with the Unicode output.
  3. Set the page charset to UTF-8. Ensure every page has <meta charset="utf-8"> in the <head>. Modern WordPress and most CMSes already do this.
  4. Declare the language. Add lang="ta" on Tamil pages (or on the Tamil sections) so search engines and screen readers know the content is Tamil.
  5. Remove forced font files. Delete CSS that forces a Bamini/SaiIndira font — Unicode text should render with the device’s own Tamil font.
  6. Keep URLs the same where possible. If a URL must change, add a 301 redirect from the old URL to the new one so you keep existing link value.
  7. Update titles and meta descriptions to Unicode Tamil too — these are also indexed.
  8. Resubmit your sitemap in Google Search Console and request re-indexing of the converted pages.
  9. Verify. After a crawl, check Search Console’s coverage and search for a unique Tamil phrase from your page to confirm it now appears.
✅ Do not delete the old pages. Convert them in place (or 301 to the new versions). Deleting and re-creating loses the page history and any backlinks pointing to them.

Which Encoding Should You Use in 2026?

One word: Unicode (UTF-8). Every modern phone, computer, browser, social media platform, and search engine supports Unicode Tamil. There is no practical reason to create new Tamil content in any other encoding.

Specifically:

  • New websites → UTF-8 encoding (default on WordPress, most CMSes)
  • Word documents → .docx format automatically uses Unicode
  • Social media → Native Unicode support everywhere
  • Mobile apps → Unicode is the only realistic option
  • Legacy content → Convert to Unicode using the tool above

Glossary of Tamil Encoding Terms

Quick definitions of the terms used throughout this guide.

Character encoding
The rulebook that maps each character to a number so computers can store and exchange text.
Code point
The unique number assigned to a character in a standard. For Tamil “க” the Unicode code point is U+0B95.
ASCII
The original 128-character encoding for English letters, digits and punctuation — the foundation other encodings extended.
ANSI (extended ASCII)
Encodings that used the extra 128 positions (128–255) for other characters. Legacy Tamil fonts like Bamini work this way, which is why they are not portable.
TSCII
Tamil Script Code for Information Interchange — an early unified, documented Tamil standard, now obsolete after Unicode.
Unicode
The global standard that gives every character on earth its own permanent code point. Tamil lives in the block U+0B80–U+0BFF.
UTF-8
The most common way to store Unicode in files and send it over the web — used by the large majority of websites.
Glyph vs character
A character is the abstract letter (க); a glyph is one visual drawing of it. One character can have many glyphs across different fonts.
Vowel sign (matra)
A mark added to a consonant to change its vowel, e.g. the ா in கா. Unicode stores these separately and combines them with the base consonant.
Pulli
The dot (்) that removes the inherent vowel from a Tamil consonant, e.g. க் .
Aytham
The special Tamil character ஃ.

Frequently Asked Questions

What is the difference between Bamini and Unicode?
Bamini stores English character codes and uses a custom font file to display them as Tamil — remove the font and the text breaks. Unicode stores actual Tamil character codes that are internationally standardized — they work on every device automatically. For a detailed comparison, see the Bamini vs Unicode Guide.
Is TSCII still used anywhere?
Practically no. Some very old Tamil websites from the early 2000s may still contain TSCII-encoded content, but no new Tamil content is being created in TSCII. Unicode has completely replaced it.
Why were so many different Tamil encodings created?
Because Tamil computing began before Unicode was widely adopted. During the 1990s, developers in Tamil Nadu, Sri Lanka, and the diaspora independently created their own encoding systems with no coordination. Unicode finally unified everyone under one universal standard. Read the full history of Tamil fonts for context.
Can old Bamini documents be converted to Unicode?
Yes. The Tamil Font Generator can convert Bamini text to Unicode instantly. Paste the text, select the encoding, and copy the Unicode output.
What do the 72 Tamil Unicode code points cover?
They cover Tamil vowels (அ,ஆ,இ…), consonants (க,ங,ச…), vowel signs/matras (ா,ி,ீ…), the Pulli sign (்), Aytham (ஃ), Tamil digits (௦-௯), and special symbols. The 216 consonant-vowel combinations are formed by combining base consonants with vowel signs — they do not need individual code points.
Which encoding should I use for a new Tamil website in 2026?
Always Unicode (UTF-8). It is the universal web standard, works on all browsers and devices, is Google-indexable, supports accessibility tools, and requires no font downloads. Legacy encodings like Bamini or TSCII should never be used for new content. Most modern CMS platforms including WordPress use UTF-8 by default.
How to check if my Tamil text is in Unicode?
Copy the text and paste it into any modern browser search bar, WhatsApp, or Google Docs. If it displays as readable Tamil, it is Unicode. If it appears as random English letters or symbols like “$hj brnj$”, it is a legacy encoding like Bamini and needs conversion.
What is UTF-8 and how is it different from Unicode?
Unicode is the character standard that assigns numbers to characters (e.g., க = U+0B95). UTF-8 is one of the ways to store those numbers in files or transmit them over the internet. UTF-8 is the most popular encoding format for Unicode and is used by 98% of websites globally. Think of Unicode as the vocabulary and UTF-8 as the way to write it down.
Can Google search find Tamil content in Bamini or ANSI encoding?
No. Google can only index Unicode Tamil text. Bamini and other ANSI-encoded content appears as English gibberish to search engines, so they will never rank in Tamil search results. This is a major reason old Tamil websites lost visibility after Unicode adoption. If you own a legacy Tamil site, migrating to Unicode is essential for SEO.
Does Unicode Tamil work in older MS Word files?
Yes, MS Word has supported Unicode Tamil since Word 2003. Files saved in .docx format store text as Unicode by default. Very old .doc files created with Bamini or SaiIndira may show garbled text — those need font-based conversion before opening in modern Word. Use our converter tool to migrate them.
📚 Sources & References: This guide is based on official documentation from the Unicode Consortium (unicode.org), the Tamil Nadu Government IT Department’s Tamil computing standards, and the historical archives of TSCII (Tamil Script Code for Information Interchange). All technical claims about code points, Unicode blocks (U+0B80–U+0BFF), and encoding compatibility have been verified against the current Unicode 16 specification.
RK

Ravindra Kumar

Independent Tamil-language website operator. This guide is written from hands-on work migrating legacy Tamil content to Unicode, and the technical details — code points, the U+0B80–U+0BFF block, and encoding compatibility — are checked against the Unicode Standard. For corrections or questions, use the contact page.

2 thoughts on “Tamil font Encoding Guide (2026)”

  1. Pingback: Tamil Font Not Showing? 5 Fixes Android & iPhone (2026) - Tamil font Empire

  2. Pingback: Bamini vs Unicode Tamil Font — Difference & Guide (2026) - Tamil font Empire

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top