ChatGPT Sees Majority Non-English Consumer Use

More than half of active ChatGPT users on Individual consumer plans now predominantly use a language other than English, OpenAI said in Signals data published June 30, 2026. For practitioners, the shift changes evaluation priorities, localization requirements, and dataset composition for real-world deployments. OpenAI reports the most common non-English languages are Spanish, Portuguese, and Arabic, and that relative user growth has been fastest in Africa and Asia, with lower-HDI countries showing the largest relative increases. The dataset covers Individual plans (Free, Go, Plus, Pro) and excludes Enterprise, education, and Codex usage. Search Engine Journal's coverage highlights rapid growth in smaller languages such as Uzbek, Kazakh, and Burmese among languages with over 1 million users.
For AI teams and product builders, the shift to a majority non-English ChatGPT user base changes what counts as a representative test suite. Models and pipelines calibrated on English-dominant inputs will systematically undercount errors and blind spots when deployed globally. Teams operating multilingual systems should reassess tokenization choices, prompt templates, and feedback collection to match actual usage distributions. From an ML ops standpoint, the fastest growth in Africa and Asia, and among lower-HDI countries, raises the practical importance of lightweight, latency-tolerant inference, mobile-first UX, and low-bandwidth evaluation.
What happened
According to OpenAI's published Signals data (June 30, 2026), more than half of active ChatGPT users on Individual consumer plans now predominantly use a language other than English. OpenAI reports that the most common non-English languages are Spanish, Portuguese, and Arabic, and that, measured from a July 2023 baseline, weekly active users grew across every continent with the fastest relative growth in Africa and Asia. OpenAI further reports that lower-HDI countries had the fastest relative growth and that among languages with over 1 million users, Uzbek, Kazakh, and Burmese showed the largest increases in June 2026. OpenAI notes the analysis covers Individual plans (Free, Go, Plus, Pro) and excludes Enterprise, education, and Codex use; the sample is based on 0.1% of accounts created between 2025-10-15 and 2026-05-01, with activity through 2026-05-31 (OpenAI Signals). Search Engine Journal's coverage of the same data set separately confirms the Uzbek/Kazakh/Burmese growth figures (Search Engine Journal).
Technical context
For teams training or fine-tuning models, these findings underscore the importance of multilingual evaluation suites and per-language error analysis. Generic English-centric benchmarks may misrepresent user-facing quality where Spanish, Portuguese, Arabic, or lower-resource languages dominate. Practitioners should consider expanded sampling in telemetry, language-aware tokenization, and evaluating safety and hallucination patterns across languages rather than relying on English proxies. Smaller languages' rapid growth (Uzbek, Kazakh, Burmese) underscores the need for low-resource language support in embeddings, retrieval, and instruction-following evaluation.
What to watch
Whether OpenAI or competitors publish per-language performance metrics and disclosure on language-specific safety outcomes, and product adjustments such as localized UIs or pricing that affect usage patterns. Also watch for third-party datasets and tooling targeting Uzbek, Kazakh, Burmese, and other fast-growing languages for downstream fine-tuning and evaluation.
Key Points
- 1Majority non-English usage shifts evaluation needs, making multilingual test suites and per-language telemetry essential for deployments.
- 2Fastest growth in Africa and Asia suggests mobile-first, low-bandwidth engineering and model latency constraints will matter more.
- 3Rapid increases in smaller languages highlight demand for low-resource language tooling, tokenization fixes, and language-specific safety checks.
Scoring Rationale
Notable for ML practitioners and product teams because it changes the distribution of real-world inputs and therefore evaluation, monitoring, and localization priorities. Not a model or architecture breakthrough, but it materially affects deployment practices. Score unchanged from prior audit.
Sources
Primary source and supporting public references used for this report.
Practice with real Ad Tech data
90 SQL & Python problems · 15 industry datasets
250 free problems · No credit card
See all Ad Tech problems