What Does It Cost to Localize a 50-Page SaaS Website Into Japanese?

No responsible vendor can quote the cost of localizing a 50-page SaaS website into Japanese from the page count alone. Cost depends on how many English source words are translatable, how much copy repeats, who reviews the Japanese, which tools the team already pays for, how engineering and QA hours are priced, and whether the site keeps changing after launch. This guide provides a transparent, recalculable model with named variables, published rate anchors, and illustrative low, mid, and high scenarios. Those scenarios are planning inputs, not quotes or guarantees.

Independent guide. This model is based on current public documentation and rate guidance, not hands-on testing. Japan Legible has no commercial relationship with Gengo, OneSky, Lokalise, or Crowdin. All product links are direct, non-affiliate links. Official pages were checked on August 11, 2026, and every price is time-bound.

Short answer

The page count is not a cost input. The same 50-page label can describe a sparse marketing site, a dense documentation library, or a mix that also includes product UI strings, support copy, and legal pages. The total cost model below starts from measured source-word volume, then adds human review, tooling, engineering, QA, tax or currency handling, and a repeating update allowance. Its deliberately wide illustrative scenarios use 12,000, 40,000, and 90,000 translatable words and produce first-pass totals from about $5,600 to about $89,000 before tax and FX conversion. Those inputs are invented to demonstrate the formula; they are not observed market ranges or prices anyone should expect to be quoted.

Why "50 pages" is not enough

Buyers start with a page count because it is visible. Vendors and tools price against words, characters, strings, hours, seats, and project phases. A pricing conversation can begin only after the site is converted into those units.

The first conversion is from pages to source words. For illustration only, one page might contain 400 words while another contains 2,500 or 4,000; these are invented examples, not observed norms. Without a string audit, nobody knows whether the site matches the 12,000-, 40,000-, or 90,000-word planning scenarios used later in this guide.

The second conversion is from total words to translatable words. SaaS sites contain repeated navigation, footer text, empty states, error messages, and template copy. Repeated strings reduce cost, but they also create consistency work: the same Japanese phrase must be used every time the string repeats.

The third conversion is from a one-time task to an operating process. Japanese pages need review, metadata, image text, terminology, and updates. The tool that creates the URLs and the human who approves the copy are separate decisions; see our website translation guide.

The seven variable groups

| Variable group | What to count | Why it matters | | --- | --- | --- | | Source volume | Translatable English words or characters, after removing repeated strings | Drives translation and review cost | | Human translation rate | Price per source word or per Japanese character for the specific language pair and domain | The largest single line when content is heavy | | Review rate | Price per word for a separate human review pass | Catches terminology and claim errors | | Tool months | Platform seats or subscriptions for the translation workflow | Recurs monthly and scales with language count | | Engineering and QA hours | Integration, URL architecture, metadata, rendering, layout, and regression testing | Often larger than translation in app-heavy sites | | Tax and currency | Consumption tax, FX assumptions, invoice currency | Converts the model into a budget the team can pay | | Contingency | Percent added for scope drift, glossary fixes, and rework | Converts an estimate into a defensible range |

These groups are the model's skeleton. Any proposal that merges them into one vague "localization fee" hides the largest risks: review depth, engineering scope, and update cadence.

The calculation

The model is arithmetic over the variable groups:

1. translation = translatable_words x translation_rate_per_word
2. review = review_words x review_rate_per_word
3. tooling = monthly_platform_cost x months
4. engineering_and_qa = engineering_hours x engineering_rate + qa_hours x qa_rate
5. first_pass_total = (translation + review + tooling + engineering_and_qa) x (1 + contingency)
6. annual_operating = recurring_monthly_budget x 12

Tax is not inside the formula because rates and rules vary by entity and jurisdiction. If the budget must be expressed in JPY, convert each line with the team's own planning FX rate and state the rate. This guide makes no tax or FX claim.

The formula deliberately keeps translation and review separate. A translation vendor's "proofread" line and a marketing owner's line-by-line Japanese review are not the same cost or the same quality gate.

What the official sources document

JTF fee guidance and style guide

The Japan Translation Federation (JTF) publishes client-facing guidance for the average translation order price paid by companies. For English-to-Japanese computer-manual translation, the guidance lists about JPY 28 per English source word, excluding tax. For Japanese-to-English, it lists about JPY 20 per Japanese character, excluding tax. JTF states explicitly that these are general average examples by field, that they vary substantially with specialty, difficulty, volume, deadline, format, processing, and quality level, and that receiving-side pricing policy also causes differences. They are guidance, not quotes.

JTF also publishes a free Japanese standard style guide for translation, first released on January 30, 2012, to reduce fluctuation in Japanese notation in professional translation. A glossary and style guide are not optional polish in a SaaS localization; they are the mechanism that makes repeated strings stay consistent.

JTF industry survey

JTF states it has conducted industry surveys since 2004, added interpretation in 2017, and released the 2024 survey report on July 25, 2025. The page says the report includes post-editing fee data for both language directions. This guide did not read the PDF, so it uses no numbers from it.

Gengo and OneSky

Gengo's public pricing table, checked on August 11, 2026, lists English-to-Japanese translation at $0.07 per word through the API and $0.08 per word through the web interface in one tier, and $0.13 and $0.14 per word respectively in the next tier. OneSky lists translation from $0.05 per word and review from $0.04 per word. Both are vendor-published list prices, not negotiated rates, and both can change.

Lokalise and Crowdin

Lokalise's pricing page, checked on August 11, 2026, listed Explorer at $144 per month, Growth at $375 per month, and Advanced at $999 per month, with Enterprise on request. Those are moving prices and should be rechecked before budgeting. Crowdin organizes pricing around hosted words and managed services with a free tier; specific plan prices were not extracted during this research, so this guide does not state them.

The platform layer is worth modeling because localization is recurring. If the site updates quarterly, the platform cost repeats long after the first translation invoice is paid.

Illustrative low, mid, and high scenarios

The scenarios below use fabricated inputs. They are not quotes, market averages, or a claim about what any vendor will charge.

| Line | Low | Mid | High | | --- | --- | --- | --- | | Translatable English words | 12,000 | 40,000 | 90,000 | | Translation rate per word | $0.08 | $0.13 | $0.18 | | Review rate per word | $0.04 | $0.06 | $0.09 | | Translation subtotal | $960 | $5,200 | $16,200 | | Review subtotal | $480 | $2,400 | $8,100 | | Tooling months | 2 | 6 | 12 | | Tooling rate per month | $144 | $375 | $999 | | Tooling subtotal | $288 | $2,250 | $11,988 | | Engineering and QA hours | 35 | 105 | 230 | | Blended engineering and QA rate | $90 | $110 | $140 | | Engineering and QA subtotal | $3,150 | $11,550 | $32,200 | | Contingency | 15% | 20% | 30% | | Estimated first-pass total, pre-tax, before FX | about $5,600 | about $26,000 | about $89,000 |

The table also assumes an ongoing update budget that is not included in the first-pass total: about $300, $1,200, and $4,000 per month in the three scenarios. Those recurring lines exist because SaaS content changes; a one-time number becomes stale by the first product launch.

Lines that cannot be zero

A defensible budget assigns a non-zero line to each of the following:

• a separate human review of Japanese copy, not just a machine check;
• a glossary and terminology review per page family;
• Japanese SEO metadata: titles, descriptions, slugs, hreflang, and structured data;
• text inside images, screenshots, illustrations, and video;
• engineering time for URL architecture, rendering, layout expansion, and responsive testing;
• QA on the Japanese site in Japanese browsers and devices;
• a recurring update allowance after launch.

Zeroing any of these produces a lower number and a different product. The marketing team may approve copy, but someone still has to write the metadata, rebuild the screenshots, and retest the flow.

What users report

A public r/TranslationStudies thread asks how much Japanese-to-English and English-to-Japanese translators typically make. It is low-confidence, user-reported evidence about translator-side economics, not a market rate table and not proof of what a buyer will pay. It matters because buyer-side quotes are shaped by translator availability and rate expectations, but this guide does not use it to derive a number.

Two editor-confirmed r/SaaS threads about localization cost could not be retrieved; they are recorded as access-limited and are not used as evidence.

Counterarguments

The strongest objection to this model is that a vendor can quote a flat project fee without all these variables. That is true, but a flat fee still embeds the same assumptions: word volume, review depth, tooling, engineering hours, and contingency. The model simply makes those assumptions visible. If a vendor's flat fee is much lower, ask which lines were zeroed.

A second objection is that machine translation plus light review can cut the translation line dramatically. That is a legitimate operating strategy, but it shifts cost into review, glossary work, and QA. The model handles that shift naturally: lower translation rate, higher review hours.

A third objection is that engineering hours dominate the high scenario and feel inflated. Engineering and QA are usually the least predictable line because they depend on the site's framework, the translation delivery method, and the team's familiarity with Japanese layout constraints. If the engineering line feels wrong, that is exactly the variable to price with a quote, not a guess.

Unknowns and prohibited overclaims

This guide does not claim:

• that any vendor will quote the scenario totals;
• that JTF's average figures are market prices or apply to a specific site;
• that Gengo, OneSky, Lokalise, or Crowdin prices will remain current;
• that the JTF white-paper PDF contains the figures this guide would need, because it was not read;
• that the r/TranslationStudies thread proves any rate;
• that a specific FX or tax treatment applies to the reader.

The central unknown is the reader's own site. Until the source strings are counted and the review and engineering scope is specified, no honest total exists. The model's output is a defensible planning range, and the next step is a string audit and vendor quotes.

Next steps

1. Export all source strings and count translatable words after deduplication.
2. Name the review owner and the glossary owner for Japanese.
3. List the pages and assets that contain Japanese SEO metadata and image text.
4. Get engineering and QA hours from the team that owns the site.
5. Run the model with low, mid, and high inputs, then ask vendors to quote the same variable list.
6. Budget an update allowance and recheck platform prices before each renewal.

For the tool-layer decision about how to create and operate crawlable Japanese URLs, start with our website translation guide. For current list prices, review the official pages directly: JTF translation fee guidance, Gengo pricing, OneSky pricing, Lokalise pricing, and Crowdin pricing.