Building a website in Thailand differs from building one elsewhere in five concrete ways: PDPA consent rules, .co.th domain paperwork through THNIC, Thai typography that breaks Western line spacing, PromptPay-first checkout, and hosting placed for Thai latency. Ignore these and your site works technically but loses Thai users.
A Bangkok agency launched a clean, fast site for a foreign-owned retailer last year. The owner loved it. Thai customers abandoned the checkout in droves, because the address form demanded a state and a ZIP code that Thai addresses do not use. The site also collected emails with no consent mechanism, which put it outside PDPA from day one. Building a website in Thailand goes wrong exactly here, when a team treats it as a translated Western build.
Building a website in Thailand is not the same job as building one in London or Sydney. The code is identical. The context is not. Compliance, domains, typography, payments, and hosting all diverge from Western defaults. Every one of those gaps stays invisible until a Thai user hits it.
Here is what actually changes, and how to plan for it before launch rather than after.
What Changes When Building a Website in Thailand
Most of building a website in Thailand looks exactly like building one anywhere. The differences cluster in five places, and those five decide whether Thai users trust you and complete.
Start with the legal layer. Thailand’s Personal Data Protection Act (PDPA) governs how your site collects and stores personal data, and it has applied to any business serving Thai users since June 2022.
Your domain comes next. A .com works fine, but a .co.th signals a registered local business, and earning one means clearing THNIC’s paperwork.
Typography is the third divergence. Thai script stacks vowels and tone marks above and below the line, so Western spacing defaults clip characters and make your text look broken to a Thai reader.
Payments diverge sharply too. Thai shoppers reach for PromptPay and wallets like TrueMoney long before a credit card, so a card-only checkout leaves money on the table.
Infrastructure is the last piece. Where your server sits changes page speed for Thai visitors, though not always in the direction people assume.
Everything else carries over. The HTML, the CMS, the hosting stack, and the SEO fundamentals behave the same. Good web design that converts traffic into leads follows the same principles here as anywhere. Treat these five as the local layer you add on top, not a reason to start from scratch.
Get these five wrong and the site fails quietly, one abandoned form at a time. Get them right and you have removed friction your competitors still ship with.
PDPA Compliance: What Your Website Legally Needs
Your website needs four things to meet PDPA: a consent mechanism, a privacy notice, a lawful basis for the data you collect, and a way for users to exercise their rights. Thailand’s PDPA took full effect on June 1, 2022. It applies to any organisation that processes the personal data of people in Thailand, including foreign companies with no local office.
A PDPA-compliant website does five things in practice. First, it shows a consent banner before any non-essential cookie or tracker fires. That banner needs an explicit accept and an equally easy reject, not a single “OK” button. Second, a plain-language privacy notice sits at the point of collection. Third, each consent is logged with a timestamp and the policy version, so you can prove it later. Fourth, users can access, correct, or delete their data without opening an account. Fifth, someone is accountable, which usually means a Data Protection Officer once you process data at scale. Break these and Thailand’s Office of the Personal Data Protection Committee can levy fines up to five million baht, with criminal liability for serious breaches.
What a compliant cookie banner looks like
A compliant cookie banner is not a decorative strip that reads “we use cookies.” It blocks non-essential scripts until the user opts in, offers granular toggles for categories like analytics and marketing, and lets users change their mind later. If your banner drops Google Analytics before the user clicks accept, it is not compliant, however nice it looks.
One caution. This is implementation guidance, not legal advice. PDPA enforcement detail shifts, and edge cases around lawful basis and cross-border transfers deserve a Thai lawyer’s read before launch.
Build consent in at the start. Retrofitting a banner and a data-request flow onto a finished site costs more than doing it during the build.
Domains, Hosting, and Where Your Server Should Sit
Two infrastructure decisions matter more in Thailand than elsewhere: whether to register a .co.th domain, and where to put your server. Neither has a default right answer, and both reward thinking through before you buy.
Do you need a .co.th domain?
A .co.th domain tells Thai users you are a registered local business, which carries trust a .com does not. Earning one means clearing THNIC, the national registry. You need a Thai company registration document, or a Thai trademark certificate that matches the domain name exactly. The name cannot be an abbreviation or extension of your company name. Each company gets one .co.th tied to its registered name, and more come only through registered trademarks. If you do not hold a Thai trademark yet, obtaining one can take months. So a .co.th is rarely a launch-week decision.
For most foreign-owned SMEs, the practical path is a .com at launch and a .co.th added once the local entity and paperwork are in place.
Local server or global CDN?
Server location is the decision people get wrong on instinct. The instinct says a server in Thailand is faster for Thai users. Sometimes it is. But a well-configured global CDN with edge nodes serving Bangkok often beats a single Thai origin server. It caches content close to the user, without the overhead of running a local host. Google treats page experience and Core Web Vitals as ranking inputs. Speed is an SEO decision as much as a UX one.
Do not choose on nationality. Choose on measured latency and Core Web Vitals for real Thai visitors, which is the same discipline behind technical SEO in Bangkok.
Test both against a Bangkok location before you commit. The fast option is whichever one your Thai users actually experience as fast.
Inspira Insight
At Inspira Digital Agency, we worked on web-facing build details for Bangkok Airways and watched how much Thai-language rendering shaped the result. The lesson that stuck: teams sign off on a design in English, then never proof the same layout in Thai, where stacked tone marks and longer strings break the spacing that looked perfect in Latin. We now treat Thai proofing as a separate QA pass, not a translation step. A design that passes in English can still fail in Thai.
Thai Typography: Why Your Site Looks Wrong to Thai Readers
Your site looks wrong to Thai readers because Western typographic defaults assume a single-level script, and Thai is not one. Thai stacks up to two marks above a base consonant and one below, so the spacing that frames Latin text cleanly crushes Thai text.
Thai typography breaks Western defaults in four specific ways. Line height is the first. A line-height of 1.4 to 1.5, comfortable for English, clips the tone marks that sit above Thai vowels, so Thai body text needs roughly 1.6 to 1.8 to breathe. Font size is the second. Thai glyphs carry detail in loops and marks that vanish at small sizes, so Thai often needs one to two pixels more than the Latin it sits beside. Font pairing is the third. A Latin display face with a mismatched Thai fallback looks incoherent, so pair intentionally or use a multi-script family like Noto Sans Thai, IBM Plex Sans Thai, or Sarabun that draws both scripts consistently. Webfont weight is the fourth. Thai glyph sets are large, so subset the font and set font-display to swap, or the page stalls on load.
Word breaking and choosing a typeface
Word breaking is the trap underneath all of this. Thai does not put spaces between words, so a browser cannot break lines the way it does in English. Set lang="th" on Thai content and let the browser’s dictionary-based line breaking do its job, or you get words split mid-syllable.
The font choice itself carries a message. Looped faces like Sarabun read as traditional and stay legible in dense body text. Loopless faces like Prompt and Kanit read as modern and Western-friendly, but lose a little legibility in long passages. Pick for the content, not the mood board.
If your Thai text looks cramped or clipped, the cause is almost always line-height and font choice, not the translation. Fix the type before you touch the copy.
Payments, Forms, and the Thai Checkout Problem
The Thai checkout problem is simple to state: Thai shoppers do not pay or fill forms the way Western ones do, and a checkout built on Western assumptions loses them. Fix the payment methods and the address fields, and abandonment drops.
Start with payments. PromptPay is the default way Thais pay online. It is Thailand’s national QR system, overseen by the Bank of Thailand. Card ownership sits far lower than in Western markets, around 22.6% by World Bank figures. A checkout that only takes Visa and Mastercard ignores how most of the country actually pays. Offer PromptPay and at least one wallet, usually TrueMoney or Rabbit LINE Pay, alongside cards.
For the gateway itself, Inspira recommends Opn Payments (formerly Omise) for most SME builds, because a single integration covers cards, PromptPay, TrueMoney, and mobile banking, and it drops cleanly into WooCommerce. For higher-volume or enterprise merchants, 2C2P is the stronger option, with broader local coverage and regional reach.
Build the address form for Thailand
Next, the address form. Thai addresses do not fit a Western schema. They use a house and village number, a soi (lane), a subdistrict (khwaeng in Bangkok, tambon elsewhere), a district (khet or amphoe), a province, and a postal code. There is no “state,” and forcing one produces confusion, abandoned carts, and undeliverable orders. Build the form around the Thai structure, not a US template with the fields renamed.
Then LINE. Most Thai businesses need a LINE presence for support, and adding LINE chat to the site is usually worth it. LINE login is a separate call: add it only if your audience expects a fast social sign-in, and skip it if a standard email or PromptPay flow already gets them through. Do not bolt on LINE login because a competitor has it.
Match the checkout to how Thais pay and where they live. That one alignment recovers more revenue than most redesigns.
How Building a Website in Thailand Reshapes Your Timeline
The five local differences do not just change the site. They change the project plan, and three of them add lead time that a Western brief never budgets for.
Domain paperwork is the first delay. If you want a .co.th and do not yet hold a Thai trademark, factor in months, not days, because the trademark route runs on the Intellectual Property office’s schedule, not yours.
Payment gateway approval is the second. Onboarding with a gateway like Opn or 2C2P involves business verification and document checks, so start the application early rather than in the final launch week.
Thai content and font testing is the third. Budget a dedicated QA pass to proof every template in Thai, checking line-height, clipping, and form fields with real Thai strings, not lorem ipsum.
Compliance sign-off runs alongside all of it. Build the consent flow and privacy notice during development, and leave room for a legal review before launch.
Cost and platform choice sit outside this article by design. If you are weighing budget, see what a website costs in Thailand, and if you are choosing a stack, WordPress or a custom build covers that call. If you are replacing an existing site, plan the migration carefully, because it is far easier to recover from a traffic drop after a redesign when you saw it coming.
Sequence the local work first. The parts unique to Thailand carry the longest lead times, so they belong at the front of the plan, not the end.
Frequently Asked Questions
How much does it cost to build a website in Thailand?
Costs vary widely by scope, from a simple brochure site to a custom ecommerce build, so a single number would mislead. Platform, page count, custom design, and integrations all move the figure. Thailand-specific work like PDPA setup, a .co.th domain, and payment gateway onboarding adds to it. For realistic ranges, see our full breakdown of what a website costs in Thailand.
Do I need a .co.th domain for a Thai business?
No, a .co.th is not required. A .com works for any Thai business. A .co.th signals a registered local company and can build trust with Thai users, but earning one means clearing THNIC with a Thai company registration or a matching trademark. Many foreign-owned SMEs launch on a .com and add a .co.th later, once the local entity and paperwork are ready.
Does my website need to be PDPA compliant?
Almost certainly yes. Thailand’s PDPA applies to any organisation processing the personal data of people in Thailand, including foreign companies with no local office. If your site uses a contact form, analytics, or tracking cookies, it collects personal data and needs a consent mechanism, a privacy notice, and a way for users to exercise their rights. Treat compliance as a build requirement, not an afterthought.
Should my website be in Thai, English, or both?
Both, in most cases. Foreign-owned businesses often launch in English and lose Thai customers who would have converted in their own language. A bilingual site widens reach, but it doubles the content and QA work, and Thai text needs its own typographic testing. Decide based on who actually buys from you.
How long does it take to build a website in Thailand?
It depends on scope, but plan for longer than a comparable Western build. The Thailand-specific steps add lead time: a .co.th domain can take months if you need a trademark first, payment gateway onboarding runs on the provider’s verification schedule, and Thai content needs a dedicated QA pass. Start the domain and gateway applications early, because they gate your launch date.
Conclusion
The single thing to remember about building a website in Thailand is that the local differences are structural, not cosmetic. PDPA, .co.th, Thai typography, PromptPay, and server placement each change the build, and each is cheapest to handle at the start rather than bolted on after a launch that already lost users. You now know where a Western template quietly fails a Thai audience, and how to plan around it. If you want a second set of eyes on a build or a live site, request a free consultation with Inspira Digital Agency and we will review it with you.
