Tamil Unicode to HTML Entity

Pick the Format for Your Destination

Start with Text to Codes and paste Tamil or mixed text. Every output has its own Copy button. All characters are encoded in the entity, CSS and JavaScript outputs, including spaces and punctuation. The URL output follows component encoding, so some safe ASCII characters remain visible. Open Character Breakdown to inspect the first 200 code points; the total count still includes the whole input.

HTML numeric references use decimal or hexadecimal code point values and end with a semicolon. The hexadecimal form starts with &#x. JavaScript output uses \u and four hex digits for each UTF-16 code unit. CSS output ends every numeric escape with a space so the next hexadecimal-looking character cannot be absorbed into the escape.

These are string representations, not complete HTML, JavaScript or CSS files. For JavaScript, JSON and CSS, add the surrounding string quotes required by your destination. Do not paste HTML entities into a JavaScript string expecting JavaScript to decode them; choose the format for the parser that will read it.

Decode Codes Back to Tamil

Switch Direction to Codes to Text. Paste one representation, then leave Decode Format on Auto Detect or select the exact format. HTML decoding accepts decimal and hexadecimal numeric references in the same input. Code point lists must contain U+ tokens separated by whitespace; byte lists use two hexadecimal digits per byte.

Auto Detect uses a fixed priority: HTML references, JavaScript escapes, U+ tokens, URL codes, CSS escapes, then byte pairs. It is intended for one format at a time. A literal piece of text that resembles an escape is ambiguous; choose a format deliberately before using the result. Decoding runs once, so double-encoded input may require a second pass.

Invalid UTF-8 bytes, out-of-range code points and unpaired JavaScript surrogates produce an error. For URL components, a plus sign stays a plus sign; this is not an HTML form decoder where plus may stand for a space. The decoded result is always inserted as text, never interpreted as markup.

Keep Tamil as UTF-8 in New Projects

For a new HTML document, save the file as UTF-8 and declare <meta charset="utf-8"> near the start of the head. You can then write Tamil directly in the source. Numeric references are useful for inspecting values or working with a constrained interchange format, but they are not necessary merely because the text is Tamil. Markup characters still need the escaping appropriate to their HTML context.

Encoding, collation and fonts solve different problems. A font draws the text; UTF-8 stores and transports it; collation orders it. Converting to entities changes the source representation without repairing missing fonts or a legacy-font encoding. The breakdown is useful when two similar-looking strings actually contain different signs.

For MySQL projects, utf8mb4 supports the full Unicode range, including supplementary characters that may accompany Tamil text. Check the connection and column character sets as well as the database default. For Excel CSV exchange, Microsoft documents opening UTF-8 CSV files normally when a BOM is present; otherwise use Data, Get Data, From Text/CSV to choose the import encoding.

The Tamil character names here come from Unicode 17.0’s character database. Spaces, Latin letters and other scripts are labelled Outside Tamil Block rather than assigned guessed names. This makes the table an exact Tamil reference while still allowing you to convert mixed-language content.