FaithGPT is becoming easier to use in the language you actually pray, study, read, and think in.
We have rolled out broader multilingual support across the FaithGPT app, starting with English, Spanish, and French. This is more than a translated landing page or a few swapped labels. The goal is a language-aware FaithGPT experience: app navigation, settings, help content, blog articles, chat context, and generated devotional content should all respect the language you choose.
Why multilingual support matters for Bible study
Faith is personal, and language is personal too. Even when someone can read English, the words of prayer, Scripture reflection, confession, encouragement, and spiritual formation often land differently in a first language or heart language.
That is why this release focuses on more than public marketing copy. FaithGPT now treats your selected language as an app-level preference that can shape how the product communicates with you.
The first supported languages are:
- English
- Spanish
- French
This gives more believers, families, small groups, and ministry teams a clearer way to use FaithGPT without constantly translating the interface in their heads.
Choose your language in settings
The language setting now lives where it should: inside your FaithGPT settings. When you choose your app language, FaithGPT uses that choice across the app experience and AI responses.
This means the language selector is not just cosmetic. It becomes part of the context FaithGPT uses when helping you study Scripture, generate devotionals, understand app features, and navigate support content.
What is translated now
This release brings localization coverage across the main user-facing app surfaces outside the admin area. That includes major app navigation, mobile bottom navigation, sidebar-linked pages, feature pages, chat entry points, help content, FAQ-style pages, and the public blog experience.
The biggest visible changes include:
- App UI in supported languages
- Sidebar and mobile navigation labels
- Chat input and welcome surfaces
- For You devotional surfaces
- Image Studio and Video Studio UI
- DoctrineGuard pages and supporting components
- Live Notes pages and supporting components
- Notes, Projects, Favorites, and linked library surfaces
- Help Center articles and article detail pages
- FAQ, About, Contact, Pricing, Terms, Privacy, and Cookies routes
- Blog index, category, and article routes
The practical result is simple: when you move around FaithGPT in Spanish or French, the experience should feel intentionally supported rather than partially patched together.
Blog posts now have localized article routes
FaithGPT blog posts can now exist as language-specific article files with matching localized slugs. That matters for readers and for search engines.
Instead of sending every reader to the same English article URL, localized posts can appear at routes such as:
/es/blog/.../fr/blog/...
This release also updates the sitemap and crawl generation path so translated posts, localized help articles, and localized public routes are generated from the canonical blog data and sitemap. That prevents broken filename-derived URLs and keeps Google submission aligned with real public pages.
Your weekly faith & AI brief.
Scripture, reflection, and the AI news that matters for Christians. Free, every week.
Read this week’s issueAI responses can follow your selected language
FaithGPT is not just translating buttons. The app language is also passed through the product context used by AI-backed features. That helps FaithGPT respond in the language you selected instead of defaulting back to English.
This matters in places like:
- Chat and Bible questions
- For You devotionals
- Prayer and reflection workflows
- Scripture study tools
- Help and support flows
- Generated content metadata
The goal is consistency. If you choose Spanish, FaithGPT should not make you repeatedly ask for Spanish. If you choose French, the app should understand that French is the expected experience.
Creative tools are part of the rollout too
Multilingual support also reaches creative workflows. Image Studio and related creation tools now have localized UI coverage so users can generate Bible art, social posts, sermon visuals, and devotional images without English-only controls getting in the way.
That is especially useful for churches and creators who serve multilingual communities. A Spanish-speaking small group leader, a French-speaking ministry team, and an English-speaking family can all use the same FaithGPT tools with fewer language barriers.
What is intentionally not translated yet
We are being careful about Bible and commentary text.
FaithGPT currently supports Bible text through KJV, ASV, and YLT. Those source texts remain as they are until exact approved non-English equivalents are identified. We are not importing random substitute Bible translations or machine-translated Bible text just to say we have more versions.
The same rule applies to classic commentary bodies. Commentary UI can be localized, but the source commentary text remains source text unless an exact translated edition is approved and traceable.
That restraint is intentional. User interface copy can be translated. Scripture and commentary source texts require a higher bar.
A better daily rhythm for more people
For many users, the most meaningful part of this release will be quiet and ordinary: opening FaithGPT, seeing the app in a familiar language, reading help content without switching contexts, and receiving daily devotional support that respects the language they chose.
That is the point. Multilingual support should not feel like a separate feature hidden in a corner. It should make Bible study, prayer, reflection, and Christian creativity feel more natural from the first screen.
What comes next
English, Spanish, and French are the foundation. We will keep improving coverage, reviewing edge cases, and expanding localized content where it can be done responsibly.
This release gives FaithGPT a stronger structure for future language support: canonical localized routes, generated localized blog data, real crawl inventory updates, language-aware app context, and shared localization tests that help prevent regression.
