general tutorial · beginner · 14 min

How to Install a Thai Font on Your Phone (iPhone, Samsung, Android)

By Narongsak Chaiwong

Typography & Licensing Specialist, ThaiGraph · August 29, 2026

Information verified as of August 2026

The short answer, by phone

On a Samsung Galaxy this works properly and the font arrives as an app from the Galaxy Store. On an iPhone it half works — you can install a font, but only apps that deliberately opt in can see it. On a stock Android phone Google documents no way to do it at all. Everything below is sourced to Apple’s, Google’s, Samsung’s, Monotype’s, Canva’s and CapCut’s own documentation, fetched on 29 August 2026. Where a widely repeated instruction turns out not to be documented anywhere, this guide says so instead of repeating it.

Before you start: what “installing a font” does not do

If you came here to put a custom font on an Instagram story, a TikTok caption or a CapCut title, installing a system font will not get you there, and the reason is architectural rather than a setting you have missed. This is the single most common disappointment with this task, so it belongs at the top rather than buried at the bottom.

Apple documents the purpose in one sentence: “You can download fonts from the App Store app and use them in documents you create on iPhone.” Documents you create. Not the interface, not other people’s apps.

The developer documentation explains why. Apple’s Core Text page for CTFontManagerRegisterFontsWithAssetNames — the function a font-installer app calls — states that “On iOS, the only supported scope is [persistent], which means the fonts aren’t automatically available to other processes. Other processes can call [CTFontManagerRequestFonts] to get access to the fonts.” And Apple’s UIFontPickerViewController page is blunter still: “Directly querying [UIFont.familyNames] provides only system fonts, but the user may have additional fonts on their device. When the user selects one of these nonsystem fonts in the font picker, the system grants your app access to the font.”

Read those two together and the rule falls out. A font you install on iOS is not added to a global list that every app reads. It is invisible to an app unless that app’s developer deliberately built Apple’s system font picker into their app. An app with a hand-rolled font menu — which is what most social and video apps have, because they ship their own curated fonts — will never show it. There is no setting for this, no restart that fixes it, and no permission to grant. It is a decision made by each app’s developer.

The vendor of the most-downloaded iOS font installer says the same thing about its own product. iFont’s App Store description states: “iFont can’t change the system font; work with the keyboard; or force apps to let you customise the font.”

Where an installed font actually shows up

This is the table nobody publishes, and it is the whole answer. Every “yes” and “no” below traces to a quotation from the platform’s own documentation. Where no first-party statement exists, the cell says so rather than guessing — a guess here is what sends people into an hour of pointless troubleshooting.

The row that matters most is the one marked not tested. Plenty of pages will tell you confidently that an installed font does or does not appear in Instagram. Neither Meta, ByteDance nor Canva publishes a statement about whether their iOS apps read user-installed system fonts, so nobody writing from documentation can honestly claim either. What is documented is the mechanism — access is granted only through Apple’s font picker — and the paths that definitely work, which are further down this page.

iPhone and iPad: what Apple actually documents

Apple’s entire published procedure for installing a font on an iPhone is three steps long, involves the App Store rather than a font file, and has not changed in substance since iOS 16. Here is the complete body of Apple’s article, quoted in full, because its brevity is the point:

Install and manage fonts on iPhone You can download fonts from the App Store app and use them in documents you create on iPhone. Install fonts Go to the App Store app on your iPhone. Get an app containing fonts. Open the app to install the fonts. Manage fonts Go to the Settings app on your iPhone. Tap General, then tap Fonts.

Three things are worth noticing about what is not there. The article never mentions a .ttf or .otf file — the string .ttf does not occur anywhere in the page. It never mentions the Files app. It never mentions AirDrop. The version selector at the top of the page covers iOS 26, 18, 17, 16, 15 and 14, and the mechanism is the same across all of them.

The second heading is also worth reading carefully. Apple calls it “Manage fonts”, not “Add fonts”. Apple documents no way to install anything from inside Settings → General → Fonts; that pane lists what is already installed and lets you remove it. Any instruction that tells you to tap an “add” button there is describing something Apple does not document.

So what do the installer apps actually do? They build an Apple configuration profile.

The configuration profile, and its four hard limits

Under the surface, every iOS font installer produces an Apple configuration profile containing Font payloads, and that payload format imposes four constraints that explain almost every “it won’t install” report. Apple’s Device Management documentation for the Font payload states them directly.

There is a genuine contradiction here worth flagging honestly. iFont’s own listing says it accepts “.ttf, .ttc, .otf formats supported, as well as these formats compressed in a .zip” — including .ttc, which Apple’s payload spec explicitly forbids. Both statements are quoted from their sources. The reconciliation is presumably that the app accepts a .ttc as input and splits it into individual payloads, since the payload itself cannot carry a collection. We have not verified that splitting behaviour on a device, so treat it as inference rather than fact. The same listing also notes that iFont “does not currently support .suit or .dfont files.”

The PostScript collision limit is the one to remember. If a Thai font “installs but shows the wrong shapes”, or refuses to install alongside a family you already have, a duplicate PostScript name is the first thing to check — and by Apple’s own wording, the result in that situation is undefined rather than merely broken.

Stock Android: the setting Google does not provide

On a Pixel or any near-stock Android phone, there is no documented way to install or choose a typeface, and this is a verified absence rather than a hard-to-find menu. Google’s own Android accessibility documentation for text and display settings lists every text option the platform offers:

Size, weight and outline. Never a typeface. Checked by full-text search of the page as fetched on 29 August 2026, the strings “font style” and “typeface” do not occur on it at all.

That absence is the answer to a question a lot of people ask in the wrong direction. Android does have a font mechanism called Downloadable Fonts, where an app requests a family from a provider such as Google Fonts — but that is something an app developer builds into an app, not something a phone owner does. On stock Android the system font is a build-time asset of the OS image, not a user-editable preference. That is why “just install the TTF” has no meaning there: there is nothing on the device that would read it.

Every consumer route that does exist is an OEM addition. Which brings us to the one that works.

Samsung Galaxy: the working path, and why a Samsung font is an .apk

Samsung is the only mainstream phone where changing the system font is a supported, documented consumer feature — and on Samsung a font is genuinely an Android application, which is why ฟอนต์ apk is a search term at all. Samsung publishes the procedure in two phrasings. The Gulf support page gives the explicit menu path:

“To download different fonts on your Samsung Galaxy phone, go to Settings > Display > Font size and style > Font style > Download Fonts. Select and install your preferred font, then apply it from the Font Style menu.”

Samsung US deliberately avoids a fixed path, because it moves between One UI versions:

“From Settings, search for and select Font size and style. Then, tap Font size and style again. Tap Font style, and then tap Download fonts. The Galaxy Store will automatically launch; tap the Install icon next to your desired font.”

Samsung states device coverage as “most Samsung Galaxy devices, including: Galaxy S24, S25, and S26 series · Galaxy Z Fold and Galaxy Z Flip series · Galaxy A series (select models)”, and warns that “Available screens and settings may vary by wireless service provider, software version, and device model.”

Why the font is an app

Open any font listing in the Galaxy Store and look at the page’s own metadata. The MT Monumint listing carries appstore:bundle_id of com.monotype.android.font.monumint and a deep link of samsungapps://ProductDetail/com.monotype.android.font.monumint. That is an Android package name. The thing you are installing is an application that happens to contain a typeface.

Samsung’s own authoring tool confirms it from the other direction. Galaxy Themes Studio’s overview states that you “can freely design the GUI of the Galaxy smartphone without coding and create it as an APK file”, and restricts the output twice over: “Content produced by Galaxy Themes Studio only works on Galaxy smartphones” and “Content produced through Galaxy Themes Studio can only be distributed through Galaxy Store.”

The underlying technology is Monotype’s FlipFont. Monotype describes the flow exactly as Samsung’s settings behave: “Once you install a FlipFont font, just go to the ‘Font’ section in display settings to activate.” Monotype also says FlipFont fonts are available “in the Galaxy App store within Samsung devices, and through the Google Play store for other Android phones.”

Hold that last line against the previous section. A FlipFont package can only do something on a phone whose manufacturer exposes a “Font style” setting for it to register with, and Google’s Android documentation lists no such setting. We have not tested a Pixel, so this is reasoning from two sources rather than a tested result — but it is the reason a FlipFont download can install successfully and then appear to do nothing.

Why you may not find Thai fonts in the Galaxy Store

Samsung answers this itself, in its own troubleshooting list: “Region restrictions: Some fonts may not be available in certain regions due to licensing limitations.” And on whether the font will hold everywhere once applied: “Font compatibility: Some third-party apps may not support custom fonts. Test the font across different apps to ensure consistency.”

We were not able to enumerate the Galaxy Store’s Thai-script catalogue — its category and search pages are rendered by JavaScript — so we make no claim about how many Thai FlipFont packages exist. Samsung’s region-restriction note is the only sourced statement available on the point.

One more honest gap: we found no Samsung first-party documentation for a Good Lock module that installs an arbitrary .ttf as a system font. Pages describing such a procedure may be right, but Samsung does not document it, so this guide does not repeat it.

Is it safe to sideload a font .apk?

A font APK from a Facebook post or a Telegram channel is not a font file — it is an arbitrary Android application with an install-time permission set, and nothing about being “just a font” limits what it can declare. This deserves a straight answer rather than a shrug, because it is the actual risk in this topic.

Google’s Play Protect documentation describes both the protection and its limits:

“Google Play Protect checks apps when you install them. It also periodically scans your device. If it finds a potentially harmful app, it might: Send you a notification… Disable the app until you uninstall it. Remove the app automatically.” “If you install apps from unknown sources outside of the Google Play Store, Google Play Protect may ask you to send unknown apps to Google.” “It may prevent an application from being installed that is unverified and uses sensitive device permissions that are commonly targeted by scammers to commit financial fraud.” “Google Play Protect is on by default, but you can turn it off. For security, we recommend that you always keep Google Play Protect on.”

The practical position: prefer packages that arrive through the Galaxy Store or Google Play, where a store review and a named developer identity are attached to the package, and leave Play Protect on. A font is not a reason to make an exception.

The third-party font changer, and what its own listing admits

The most-installed tool in this category is zFont 3, by Khun Htetz Naing — 50M+ downloads, 3.2 stars from 288K reviews, updated 9 April 2026, carrying ads and in-app purchases. We are not recommending it. We are reporting two things its own Google Play listing says, both of which change the decision and neither of which appears on the pages currently ranking for this query:

1. Its Samsung compatibility list stops at Android 14. The listing enumerates support up to “Android 10, 11, 12, 13, 14” — Android 15 and 16, meaning One UI 7 and One UI 8, are not claimed. Written on 29 August 2026, that is the most useful sentence about this app available anywhere.
2. The OPPO, Realme and OnePlus routes work by changing your phone’s region to Myanmar. In the vendor’s own words: “On Android 10 and newer, font changes are possible if the option to switch to Myanmar region is available in settings”, and for OnePlus, “Works on Theme Store supported devices with the option to switch to Myanmar region available in settings.”

The listing’s data-safety section states the app “may share these data types with third parties: App info and performance and Device or other IDs.” Decide with that in hand.

The Thai-only failure: tofu, dotted circles and tone marks in the wrong place

A font can install perfectly, preview beautifully in English, and still be unusable in Thai — because Thai stacks up to two marks above a single consonant and a font must carry specific OpenType positioning tables to place them correctly. This failure mode is invisible until you type real Thai, and it is the reason to check a font before you go through any of the installation above.

There are two distinct problems, and they look different.

Problem one: no Thai glyphs at all. Google Fonts defines the symptom precisely: tofu is “A symbol that has come to be known as ‘tofu’, displayed when a character is not present in a font and no fallback option is available.” The Thai script occupies Unicode block U+0E00–U+0E7F. If a font has no glyphs in that range, every Thai character falls back or renders as tofu. A family name containing the word “Thai” is not evidence that it does.

Problem two — the harder one: Thai glyphs are present, but the marks land wrongly. Microsoft’s Thai script development documentation gives the vocabulary:

“Base Glyph - Any glyph that can have a diacritic mark above or below it.” “Combining Mark - A vowel sign or tone mark, positioned above or below a character to provide pronunciation guidance.” “Cluster - The effective ‘unit’ of Thai writing systems, consisting of a consonant, vowel signs, combining tone marks, and independent vowel letters.”

And the two features that do the positioning work:

“Mark to base — Apply feature ‘mark’ to position diacritic glyphs to the base glyph. Mark to mark — Apply feature ‘mkmk’ to position diacritic glyphs to other diacritic glyphs.”

Thai needs both. A cluster like ที่ puts a vowel sign above the consonant and a tone mark above the vowel sign — that second placement is mkmk. A Latin font that happens to include the Thai block, or a cheaply converted “cute font” APK, frequently ships mark without mkmk. The tone mark then sits on top of the vowel sign instead of above it, or collides with the ascender. There is a related tell for malformed input: Microsoft notes that combining marks appearing without a valid consonant base are invalid and get displayed “positioned on a dotted circle.”

Microsoft’s page describes the Windows shaping engine, so we are citing it for the definitions of mark and mkmk, which are OpenType features rather than Windows-specific ones. We are not attributing iOS or Android shaping behaviour to it.

Four checks you can run before you install anything

1. Check the release page names Thai as a supported script. On Google Fonts the family page states the languages covered.
2. Type a real Thai string with stacked marks and look at it. Use our Thai font tester with strings that exercise the hard cases: ป่า, ที่, ก็, ปู, หนึ่ง. If the tone mark on ที่ sits low or crashes into the letter above, stop there.
3. Confirm the Thai Unicode block is actually populated, not merely that the name contains “Thai”.
4. Prefer a font whose provenance you can check. Every entry in our font directory records designer, foundry and a verified licence — which also answers whether you are permitted to copy the file onto a device in the first place. See Thai font licensing.

Canva and CapCut: what most people actually came here for

For a large share of this intent the answer is not to install a system font at all — it is to upload the font into Canva, which is fully documented and works identically on both platforms. CapCut, by contrast, documents no import route whatsoever.

Canva: documented, gated, and with one trap that catches Thai users constantly

Canva’s Help Center states the gate first, and it is the sentence to read before anything else:

“Who can upload fonts? Team owners, administrators, and brand designers. Canva Pro, Canva Teams, Canva Business, Canva Education, and Canva for Nonprofits”

Font upload is not available on free Canva. The constraints, all quoted from Canva’s own pages:

Three of those hit Thai users harder than anyone else:

• .ZIP is rejected, and almost every Thai font downloads as a ZIP. f0nt.com releases and the National Font distributions both arrive zipped. You have to unzip first — on the phone, before uploading. This is the most common reason a Thai user’s Canva upload fails, and it produces an error message that does not mention the real cause.
• “Licensed for embedding” is a real gate, not boilerplate. Uploading a font to Canva is an embedding act. A free-for-personal-use font from a community site is exactly the case where that condition bites. Our Thai font licensing guide sets out which regime applies to what.
• No variable fonts. Several modern Thai families ship variable builds. You need the static instances.

We are quoting Canva’s desktop steps only. The help page has a Mobile tab, but its content is loaded by JavaScript and was not present in the page as fetched, so we are not going to invent mobile steps for you.

CapCut: a verified negative

We enumerated every support-article link served on CapCut’s Help Center index — 61 unique URLs on 29 August 2026 — and none of them covers importing, uploading or adding a custom font file. The only font-related article is “What Should I Do If I Can’t Find The Material for The Text Font or Text Template?”, dated 30 January 2026, and its entire remedy for the mobile app is to work with the built-in library:

“Tap ‘Font’ or ‘Template’ and check if the ‘Commercial Use’ filter (or similar label like ‘Licensed’) is enabled. If it is, disable it—this may hide free or non-commercial fonts/templates. … Use the search bar at the top to enter keywords… Ensure your app is updated to the latest version via the App Store or Google Play, as new fonts/templates are frequently added.”

The same page adds that “Some fonts/templates are region-restricted or require an internet connection to load.”

So, stated as carefully as the evidence allows: as of 29 August 2026, CapCut’s own Help Center documents no way to import a font file into the CapCut mobile app. Tutorials showing otherwise may be describing a build, a region or a workaround we cannot verify; CapCut itself does not document it. If you need a specific Thai typeface in a video, setting the text in Canva and bringing it in as an image or overlay is the route that rests on documentation.

Name variants and spellings

This one task is searched under a dozen different names, in two scripts, and they all land here:

• ฟอนต์ ttf มือถือ — TTF fonts for a phone, the format-led query
• ฟอนต์ โทรศัพท์, ฟอนต์มือถือ — phone fonts, written spaced or joined
• ฟอนต์ ไอโฟน, ฟอนต์ ไอ โฟน — iPhone fonts; both spacings are in heavy use and mean the same thing
• ฟอนต์ apk, ฟอนต์ซัมซุง — the Samsung route, searched by file type or by brand
• วิธีลงฟอนต์ในมือถือ, วิธีเปลี่ยนฟอนต์มือถือ — how to install versus how to change, which are different questions on iPhone and the same question on Samsung
• font samsung ttf, install Thai font on iPhone, Samsung font ttf download — the English and mixed-script equivalents
• ฟอนต์ ไอจี / ฟอนต์ ไอ จี — Instagram fonts. Usually a different task entirely: those searches almost always want a Unicode text generator, not a font installed on a device

Where to go next

This guide is deliberately device-led, so if your question is really about one particular typeface, the font’s own page is the better answer and it is one click away. Start with the checks, then the licence, then the font.

If you are trying to install one specific Thai font — most often a Sarabun variant for a government document — the font’s own page carries the correct download source, the licence, and the file-naming details that matter for that family. Start at TH Sarabun PSK, TH Sarabun New or Sarabun rather than working from a generic install guide.

Otherwise: check any font against real Thai text in the font tester before you install it, confirm you are allowed to use it with the Thai font licensing guide, browse free Thai fonts or the state-commissioned Thai National Fonts, and read the Thai typography guide for why tone-mark placement behaves the way it does.

Information verified as of August 2026