Can I write prompts in a language other than English?

Yes — write prompts in any language and the builder follows them. German, Spanish, French, Japanese, and more all work. Here's what to know about prompts versus your app's text.

Yes. Write your prompt in any language and the builder will follow it.

German, Spanish, Portuguese, French, Japanese — if you can describe what you want, the builder understands it. You don't need to translate your ideas into English first.

Prompts versus app text

The language of your prompt and the language of your app's text are separate things.

For a new app, the builder is instructed to use the language you request. If you do not specify one, it is instructed to use the language of your first prompt. Review the preview to check the result.

For an existing app, a follow-up in another language should keep the app's current language. Ask explicitly when you want its text translated.

To get your app's text in a specific language, say so explicitly:

Make all text in the app German.

Or combine it with your build request:

Build a contact form. All text and labels should be in German.

Mixing is fine

A German prompt can produce an English app, and an English prompt can produce a German one — just say what you want. There's no rule that the prompt language and the app language have to match.

Shared screens in new apps

New ClickFunnels AI and ClickFunnels AI apps include English, Japanese and Spanish translations for shared sign-in, access, account and checkout controls, navigation and dialog labels (including screen-reader labels), notification recovery prompts and app-update notices. These screens follow the app's default language. Other app languages use English for these shared controls while the builder can still write your own pages in your requested language.

Your product names, user-entered content and text inside external payment providers are separate. This does not translate every piece of content in an app. Existing apps keep their saved code; they are not automatically rewritten by a template update.

Platform language and app language

The language you choose for the ClickFunnels AI or ClickFunnels AI dashboard is separate from the language of the app you build. Changing one does not change the other.

Check the whole experience

Review navigation, forms, error messages and mobile layouts before publishing. For Arabic or Hebrew, also check reading direction, menus and mixed-language inputs.

Checkout supports a limited set of languages and may fall back to your browser language or English. Date and money formatting can use the app's language in newly created apps. Ask for the formatting you want; changing the language does not convert prices or change their currency.

Tips

  • Keep product names and technical terms consistent across prompts. If your app has a table called Bestellungen, use that name in every subsequent prompt so the builder knows what you're referring to.
  • If a word might be ambiguous across languages, a brief note helps: Add a search bar (Suchfeld) to the orders (Bestellungen) list.

Was this helpful?

Thanks for the signal — it helps us improve the docs.

More in Building apps

How to ask the AI for changes

Better prompts get better results. The short guide to writing requests the AI nails on the first try.

What the AI can — and can't — do

Realistic expectations for what you can build with ClickFunnels AI, what the AI handles, and where you might hit limits.

Where did plan mode go?

The Plan / Build toggle is gone. To talk something through without changing your app, just say so — "don't change anything yet" works.

Still need help?

If this didn't answer your question, our team is one click away.