How to sell your game in Japan: what the market asks of you

Japan usually shows up in one of three ways for a game made somewhere else. A cluster of Japanese wishlists appears that you cannot explain. A stream in Japanese moves your numbers for a week. Or a message arrives asking whether a Japanese version is planned. In every case the question underneath is the same: what would it actually take to sell here, and is it worth doing?

Japan is a market with its own discovery channels, its own expectations about written text, and a player base that overwhelmingly plays in Japanese — and notices immediately when a game does not accommodate that. None of this makes it hard to enter. It makes it hard to enter accidentally.

This article is the overview: how to read the signals you already have, what the language work really involves, where Japanese players find games, and when working with a partner beats doing it yourself.

Is Japan actually your market?

Before spending anything, spend an afternoon on the evidence you already own. Your storefront's regional data — wishlists, traffic, and sales by country — tells you whether Japanese players are finding you despite the lack of a Japanese version. Requests in your community and comments on your videos are the same kind of signal in a noisier form. So are streams: if a Japanese-language video moved your wishlists, that is a market test somebody ran for free on your behalf.

The most useful free research is comparable titles. Find games close to yours in genre, scale, and price that shipped with Japanese support, and look at the language distribution of their reviews. That distribution is a rough but real proxy for how much of that genre's audience is Japanese-reading, and it will vary far more by genre than by market size. Some genres have deep, loyal Japanese audiences; others are dominated by domestic titles that a foreign entrant will not displace.

One thing regional data cannot show you is the ceiling, because reach in Japan is limited by language in a way it is not in some European markets. In several countries a large share of players are comfortable playing in English, so an English-only release still reaches most of the potential audience. In Japan it does not. For the current picture, read the language breakdown in your platform's own hardware and software survey rather than any secondhand figure, and pair it with your own regional data.

This is also why the most common plan fails. 'We will localize into Japanese if the game sells in Japan' sounds prudent, but a game that is not in Japanese is mostly invisible to the audience that would buy it, so the test never returns a positive result. The realistic version of that plan is to localize the cheapest surface first and read the response from that.

Text quality is read as product quality

Japanese readers identify translated-feeling Japanese quickly, and the tells are structural rather than a matter of individual mistakes. Pronouns inserted where Japanese would naturally omit them, English sentence order preserved, every character speaking in the same textbook-polite register: each sentence can be grammatically fine while the whole thing reads as machine output.

Register matters more than most source-language writers expect. Japanese encodes politeness and social distance in sentence endings, pronouns, and verb forms, so a rough mercenary and a formal court official are expected to sound different in a way that goes beyond word choice. A translation that flattens every character into one neutral voice does not just lose flavor — it removes one of the main tools Japanese readers use to tell characters apart.

Mixed scripts are the other visible failure. A single English button label sitting in an otherwise Japanese menu is impossible to scan past, because the two scripts look nothing alike. Untranslated tooltips, leftover debug strings, and English error messages all stand out the same way.

The consequence is commercial, not aesthetic. Once reviews start saying the translation reads like machine output, that sentence becomes the summary of your game for every player who reads the page afterwards, and it is very hard to take back. This is why shipping fewer languages well beats shipping many badly, and why an honest English-only game with a properly translated Japanese store page is a more defensible position than a hastily machine-translated build.

The store page, the language checkboxes, and the price

The Japanese store page is the highest-leverage few hundred words in the entire project. It is small enough to have translated properly by a native speaker for a modest sum, it is what every Japanese player sees before anything else, and it works even while the game itself is still English-only — as long as you say so clearly.

Pay particular attention to the short description and to genre vocabulary. Japanese players search using Japanese genre terms, and a literal translation of your English tagline will often miss the words people actually type. When you commission the page, ask the translator for the terms players use for this kind of game, not the dictionary equivalents of your terms.

The supported-languages declaration deserves a careful pass of its own. Interface, subtitles, and audio are separate claims, and each one is checked by players who will hold you to it. Overclaiming produces refunds and disappointed reviews; underclaiming removes you from the language filter people browse with. If coverage is partial — story translated but menus not, or the first chapter only — say exactly that in the description rather than letting the checkboxes imply something you have not done.

For price, look at comparable Japanese-language titles in your genre and see what they charge in yen. Storefronts will suggest a converted figure based on your home price; treat that suggestion as a starting point rather than an answer, since it knows your currency but not your genre's local price expectations.

Where Japanese players find games

Discovery in Japan runs through channels that a foreign developer will not stumble into by accident. Video is the largest of them. Gameplay commentary videos are a mainstream way Japanese players decide what to buy, and creators in that space pay close attention to whether a game's terms permit monetized video. Publishing a clear, plainly written video and streaming policy in Japanese removes a real barrier — many Japanese studios publish exactly such a page, and its absence is read as an unanswered question rather than as permission.

Short-form social posting is the other major channel: Japanese developers and players are heavy users of X, and a short clip posted with Japanese text and Japanese hashtags travels in a way an English post does not, even to the same people. Japanese-language game media covers indie titles regularly, and a press email plus a press kit in Japanese is basic homework that most foreign developers skip — which is exactly why doing it stands out.

Events matter more here than the online-only mental model suggests. The indie areas of Tokyo Game Show, the Kyoto-based indie showcase BitSummit, and doujin-oriented events are where Japanese press and creators concentrate their attention. Exhibiting from abroad is expensive, but a local partner, a distributor, or even a friend can staff a booth, and the weeks around those events are when Japanese coverage is most available.

Finally, build a route for feedback in Japanese. Players who would never write a bug report in English will write a detailed one in Japanese, so a Japanese contact address, a Japanese channel in your community server, or a simple form surfaces problems you would otherwise never hear about — including translation errors, which are the ones your other players cannot report.

Doing it yourself versus working with a partner

A Japanese publisher or localization partner brings a bundle: translation and in-context QA, store and marketing copy, relationships with press and creators, event presence, customer support in Japanese, and sometimes console porting and the local ratings process that console releases require but PC storefronts do not. What you pay is a revenue share or fees, plus some control over timing and messaging, plus a dependency you cannot easily unwind mid-release.

The bundle is worth it when several of those pieces are things you genuinely cannot do: console plans, a physical release, a text-heavy game where translation volume is a project in itself, or a title whose Japanese potential is already visible in your data and larger than your capacity to serve. It is not worth it for a small, text-light PC game whose entire language job is a few thousand words. In that case, commission a translator directly, handle the store page yourself, and keep the margin.

If you do talk to partners, ask concrete questions and compare the answers:

• What have you shipped in my genre, and can I see the Japanese text you produced for it?
• Who does the translation, and is there a separate reviewer, or does one person do both?
• How do post-launch patches work — who translates a hotfix, and how quickly?
• What happens to the glossary and translation memory built during this project?
• Who answers Japanese customer support and reviews, you or us?

A realistic order of operations

Everything above sequences into a plan where each step is cheap relative to the next one and buys you information about whether to take it.

Build the recurring work into that plan from the start, because it is what separates a game that sold in Japan from a game that has an audience in Japan. Patch notes that stay English-only tell Japanese players the version they bought was a side project. A translation fix shipped two weeks after a player reported it says the opposite, and costs almost nothing. Budget a few hundred words a month for announcements and fixes, and find someone who can read the Japanese reviews and tell you what they say — the cheapest market research you will ever buy, and the one foreign developers most reliably never get around to.

With that in mind, the order:

• Read your own data: regional wishlists and traffic, plus review-language distribution on comparable titles
• Localize the store page properly — a native translator for a few hundred words, plus at least one localized screenshot set
• Wait a few weeks and watch what moves; a Japanese page on an English-only game still produces a usable signal
• Localize a demo or the opening hour, which converts curiosity into evidence at a fraction of full cost
• Then the full game text, followed by a review pass in the actual build rather than in a spreadsheet
• Then the ongoing part nobody budgets: patch notes, store updates, support replies, and review responses in Japanese