Is Penpot ready for the Japanese market?
— a Tokyo native's gap map

penpot.app and the pricing page render only in English. No language switcher exists anywhere in the funnel.

penpot.app/pricing

A Japanese designer or design lead evaluating a Figma alternative reads marketing in Japanese or not at all. When the entire funnel is English, they assume the product, support, and docs are English too, and drop off before signing up. This is the single highest-leverage gap because it's the first thing any buyer sees.

A Japanese landing page and pricing page, plus a visible language toggle. Estimated build: 2–3 weeks for a native-checked translation.

The footer has Terms, Privacy, Cookie policy, a DPA, and Whistleblowing. No 特商法に基づく表記 page exists.

penpot.app (footer links checked)

Before paying, Japanese buyers look for the 特商法 disclosure. It's the standard "is this a real, accountable company" check. Local SaaS shows it; its absence reads as a foreign service that hasn't set up for Japan, which makes a company hesitant to put it on a card or expense it.

A single 特商法に基づく表記 page with required fields: seller name, contact, pricing, payment timing, refund/cancellation terms. It's a known template, not a build.

Plans shown in USD: $0 (free), $7/user/month (capped at $175), $25/user/month (from $950), $50,000/year for Private Server.

penpot.app/pricing

A USD figure forces mental conversion, exchange-rate anxiety on a recurring charge, and a messy line on a Japanese invoice. For finance approval in a Japanese company, a clean JPY number is far easier to push through.

JPY display pricing (at minimum alongside USD). For enterprise deals, a JPY-denominated invoice removes the last friction for accounting.

With no Japanese pages, there is nothing indexed for the terms Japanese designers actually type. The English marketing pages do not rank for Japanese-language queries.

A Japanese designer looking for an open-source Figma option searches 「figma 代替」 or 「オープンソース デザインツール」. Penpot doesn't appear, and they land on whatever local roundup article ranks instead — usually one that mentions Canva or domestic tools. Penpot is absent from the exact moment of evaluation.

A small set of Japanese pages targeting those queries, which also gives the volunteer translation work somewhere to live. The existing community effort (issue #5128) is a head start on raw material.

github.com/penpot/penpot/issues/5128 — ja volunteer

Issue #5128 — youseiushida offered to translate Penpot into Japanese on Weblate. The issue is closed; no official Japanese locale is visible in the product.

github.com/penpot/penpot/issues/5128

When someone offered to translate and the product still shows no Japanese, a careful buyer reads that as "they started Japan and gave up." A half-finished or stalled localization can hurt trust more than no localization, because it signals the effort died.

Either ship the Japanese locale to a usable state and surface it, or set clear public expectations. Turning that volunteer energy into a visible result is cheap relative to the trust it buys.

Interface and copy follow US conventions — date format (MM/DD/YYYY), currency symbol placement, and informal register in onboarding and emails.

Smaller cues — date format, currency symbol placement, a polite 敬体 register in onboarding and emails — are what make a product feel made for Japan rather than translated at Japan. None of these alone loses a deal, but together they shift the read from "foreign tool" to "this wasn't made for us."

Locale-aware formatting plus a translation pass checked by a native speaker for register (not just literal accuracy).