# FiveM language statistics 2026: player shares by locale

**Published: 22 September 2026. Data window: 15–17 September 2026, UTC.** This is a dated research snapshot, not a live player counter or a full-year demographic survey. The server-language setup instructions were updated on **14 October 2026**; the historical data below have not been refreshed.

Is English the biggest language in FiveM? The available evidence needs a more specific answer. In FiveStats' **17 September 2026** report, `pt-BR` led the displayed locale rows at **21.8%**, ahead of `en-US` at **15.7%**. That compares two **server locales**, not everyone who speaks Portuguese or English. [Source: FiveStats daily report](https://fivestats.io/blog/fivem-daily-report-2026-09-17).

> **Server language is not player language**
> These are third-party, published player-share percentages grouped by the server's declared locale.
> They are not verified counts of unique people, native speakers, residents of a country, or QBCore-only players.

## Reported FiveM player shares by server locale

The chart and table reproduce the report's rounded percentages. **Other locales** is the calculated remainder, not an additional language. It may include regional variants of languages already listed. [Source: FiveStats, 17 September](https://fivestats.io/blog/fivem-daily-report-2026-09-17).

| Server locale | Language label | Reported share |
| --- | --- | ---: |
| `pt-BR` | Portuguese (Brazil) | 21.8% |
| `en-US` | English (US) | 15.7% |
| `th-TH` | Thai | 13.0% |
| `ar-SA` | Arabic (Saudi Arabia locale) | 11.1% |
| `fr-FR` | French (France) | 8.9% |
| `de-DE` | German (Germany) | 5.5% |
| `root-AQ` | Unconfigured / placeholder locale | 4.0% |
| `tr-TR` | Turkish (Turkey) | 3.7% |
| Other locales | Calculated remainder | 16.3% |

The displayed rows total **100.0%** after including the remainder. Values are rounded to one decimal place. Download the [chart data and source notes as JSON](/data/fivem-language-statistics-2026-09.json).

**Reading the result:** do not dismiss non-English localization on the assumption that English must dominate. Equally, this chart does not establish that all Portuguese-language activity exceeds all English-language activity. A complete language comparison would need every relevant locale grouped consistently.

## How many players does that represent?

There is no verified unique-player count by language in these reports. A daily average of concurrent connections is not a count of everyone who played that day. Someone who stays connected for several hours contributes to several observations; a language survey would answer a different question.

For scale, the following chart shows **overall FiveM concurrency**, separately from the locale percentages. The three daily reports publish these daily averages and observed peaks. [15 September](https://fivestats.io/blog/fivem-daily-report-2026-09-15), [16 September](https://fivestats.io/blog/fivem-daily-report-2026-09-16), [17 September](https://fivestats.io/blog/fivem-daily-report-2026-09-17).

| UTC date | Average concurrent players | Peak concurrent players | Scans / expected |
| --- | ---: | ---: | ---: |
| 15 September 2026 | 146,018 | 221,874 | 96 / 96 |
| 16 September 2026 | 146,463 | 218,956 | 95 / 96 |
| 17 September 2026 | 147,077 | 220,679 | 96 / 96 |

The 16 September report has one missing scan. These three observations provide context, not evidence of a long-term growth trend. [Source and coverage note](https://fivestats.io/blog/fivem-daily-report-2026-09-16).

> **Do not multiply these two charts**
> The source's locale counts do not reconcile with its daily concurrency totals. A shared denominator
> has not been verified. Multiplying a locale percentage by the daily average would create an
> unsupported estimate, not a measured count of players speaking that language.

## Why en-US is not all English-speaking players

A locale combines a language with a regional variant. The official Cfx.re example lists both `en-US` and `en-GB`, alongside values such as `fr-CA` and `pt-BR`, as server-language identifiers. It also instructs administrators to replace the `root-AQ` placeholder. [Cfx.re server configuration reference](https://docs.fivem.net/docs/server-manual/setting-up-a-server-vanilla/).

For analysis, keep two views separate. A **locale view** preserves distinctions such as US and British English. A **language view** would group all English variants together, all Portuguese variants together, and so on. Do not compare an aggregated language on one side with a single regional locale on the other.

An English-labeled server also does not establish where its players live or which other languages they understand. Multilingual communities are a reason to ask users about their preferences rather than infer personal attributes from a server listing.

## Server count and player activity answer different questions

Counting servers measures the supply of listings. Counting concurrent connections measures observed activity. These measures need not have the same ranking: many nearly empty servers can coexist with a smaller number of busy communities.

Consider a hypothetical example: 100 servers with five connected players each have 500 connections in total; ten servers with 100 each have 1,000. The first group has more servers, while the second has more activity. Neither number reveals how many unique people visited during a month.

This article does **not** publish a numerical server-count ranking. A reproducible, dated server-count dataset with clear language grouping and coverage would be needed. Mixing a changing directory count with a different provider's player-share report would imply a comparability that has not been established.

## What QBCore server owners should do with this information

Treat these figures as a starting point for questions, not a universal localization order or a revenue forecast. The observations cover FiveM across frameworks; they cannot identify the language distribution of QBCore servers alone.

**For a new community, choose a language your team can support.** Rules, onboarding, support replies, moderation, and in-game text should agree. Translating a landing page is not enough when new members cannot get help in the advertised language. The [QBCore quickstart](/quickstart) covers the initial server setup.

**For an existing server, measure your own audience.** Offer an optional language preference and compare onboarding completion, repeat participation, and support demand. Keep the question optional and avoid treating a preference as nationality. Your audience can differ from an ecosystem-wide snapshot.

**For a resource developer, separate text from logic.** Plan for translation keys, fallback text, variable interpolation, fonts, text expansion, and right-to-left layouts where needed. The chart is not a reason to discard a smaller language when actual customers need it. See [how to assess free QBCore resources](/news/best-free-qbcore-scripts-2026) before adding dependencies to a server.

### Set the server-list locale correctly

Select the community's primary language in its server record in the [Cfx Portal](https://portal.cfx.re/).
For a Brazilian Portuguese community, choose the corresponding supported language option rather than
copying a `sets locale "pt-BR"` assignment into a new `server.cfg`.

The [14 October 2026 Cfx announcement](https://forum.cfx.re/t/portal-update-server-metadata-management/5431315)
keeps existing configuration-based listing metadata working during the transition until **21 October 2026**.
From that date, language and the other public listing fields are managed in the Portal. Review any
backfilled value and fill missing information; see the [Portal migration checklist](/docs/installation/server-config#public-listing-metadata-in-cfx-portal).

The listing language advertises the language your community supports. It does not translate QBCore,
installed resources or your website. QBCore's own `qb_locale` remains a separate resource setting.
For future research, record the collection date and metadata source rather than assuming Portal-era
and earlier configuration-era locale observations are automatically comparable.

## Methodology and limitations

FiveStats describes a 15-minute scan cadence and UTC daily aggregation. It says its reports do not use player-level data, that locale labels can come from the current snapshot, and that servers which later disappear may be absent from historical tables. Its written commentary is generated automatically. We reproduce selected numerical fields, not its causal explanations. [FiveStats methodology](https://fivestats.io/blog/fivem-daily-report-2026-09-15).

Our additional safeguards are straightforward: retain the unlisted remainder, keep the placeholder separate, label the dates, preserve missing-scan information, and do not invent a language-level population from incompatible totals. The published percentages have not been independently audited against raw scans. This is **directional community research**, not an official Cfx.re census.

To improve the analysis, obtain the complete locale dataset for the same observation window, document its denominator, retain unknown values, and aggregate language variants transparently. Repeated observations across weekdays and time zones would then be more useful than treating a single date as an annual average.

## Frequently asked questions

### Is Portuguese bigger than English in FiveM?

In the selected report, `pt-BR` is above `en-US`. The article does not establish the ordering of all Portuguese and all English variants combined. Read the locale labels literally, rather than substituting whole languages for them.

### How many FiveM players speak English?

These data do not answer that question. The `en-US` share is not a survey of English proficiency, and daily concurrency does not give the number of unique English-speaking players.

### Does root-AQ mean players are in Antarctica?

No. In the Cfx.re example it is a placeholder administrators are told to replace. This article keeps it as unconfigured / placeholder, not as a geographical audience. [Configuration reference](https://docs.fivem.net/docs/server-manual/setting-up-a-server-vanilla/).

### Should every QBCore project translate into the same languages?

No fixed order follows from this snapshot. Start with the community you can serve, then prioritize demonstrated user demand and maintainable translation coverage. Player-share statistics alone do not measure sales potential or support costs.

## Sources and further reading

- [FiveStats — 17 September 2026](https://fivestats.io/blog/fivem-daily-report-2026-09-17): reported locale percentages and daily concurrency.
- [FiveStats — 16 September 2026](https://fivestats.io/blog/fivem-daily-report-2026-09-16): concurrency and incomplete scan coverage.
- [FiveStats — 15 September 2026](https://fivestats.io/blog/fivem-daily-report-2026-09-15): concurrency and collection limitations.
- [Cfx.re — vanilla server configuration](https://docs.fivem.net/docs/server-manual/setting-up-a-server-vanilla/): the meaning and configuration of server locales in the historical setup.
- [Cfx.re — Portal metadata management](https://forum.cfx.re/t/portal-update-server-metadata-management/5431315): the October 2026 migration of public listing fields.

Return to [QBCore community news and research](/news) for more independently authored articles.
