Back to Blog
Comparison 14 min read

FiveM Phone Scripts Compared 2026: lb-phone vs gks-phone vs qs-smartphone vs qb-phone

The phone is the single highest-engagement script on a roleplay server. Players check it constantly — for calls, banking, social, dispatch, music. Picking the right one shapes how 50+ other scripts feel because phone-app integrations have become the standard interaction model. This is the honest comparison, with prices, app ecosystems and the "which one should you actually buy" verdict at the bottom.

D
devCon Team
· May 30, 2026

FiveM phones have become an arms race. Each year a new generation of phone script ships better UI, more apps, deeper integrations. In 2026 there are roughly five phone scripts that matter, and the differences between them are large enough that switching mid-server is genuinely painful.

Our recommended FiveM hoster

For the CPU performance and DDoS protection FiveM needs, we recommend Avoro — German-based, Ryzen 9 7950X3D nodes, always-on DDoS, real unmetered traffic. See our FiveM hosting comparison.

This post compares them honestly — including the trade-offs the vendor pages won't tell you.

The contenders

  1. lb-phone — the dominant premium option in 2026
  2. gks-phone — the older free-ish standby, still widely deployed
  3. qs-smartphone — quasar's polished offering
  4. qb-phone — the QBCore community default
  5. yseries-phone — the underrated newcomer with strong RP-server traction

Quick verdict

For most servers in 2026: lb-phone. It's pricey but the app ecosystem (dispatch, radio, business, lifeinvader, garage integrations) is so deep that the rest of your script stack ends up feeling more cohesive than with any alternative.

For tight budgets: gks-phone still works, and there's enough community content to fill the gap.

For QBCore-first servers: qb-phone is the obvious local choice, but lb-phone now has solid QBCore support and most QBCore servers above 100 slots end up on lb-phone anyway.

Rest of the article is detail backing those calls.

lb-phone

What it is

The flagship product from LBPhone (Liberty Mods). First released late 2022, currently on version 2.8.x. Paid product, ~€75 one-time + €15 for major version upgrades. Most actively developed of any FiveM phone right now.

Strengths

  • App SDK is the real differentiator. Third-party developers ship phone apps as integrations, not as separate UIs. Garage script? Has an lb-phone app. Dispatch? Has an lb-phone app. Business management? Same. This consistency is the biggest UX win on any modern server.
  • Live Tray (the "dynamic island" equivalent) — for currently-playing music, active calls, navigation. Feels modern.
  • Active development. Major version bumps every 4-6 months with real new features, not just bug fixes.
  • Multi-framework support. Works with ESX, QBCore, Ox Core out of the box. No conversion needed.
  • Polished UI. Feels closer to a real iPhone than any competitor.
  • Active Discord community with 30k+ members — easy to get help.

Weaknesses

  • Price. €75 + €15 per major version. For small servers this is a real expense.
  • Locked update path. Major versions cost extra. If you skip a version, the upgrade gets harder.
  • Closed source. Customizing beyond config is painful — you can't easily mod the UI.
  • Heavy on the client. Larger memory footprint than the others. Not a problem on modern PCs.

App ecosystem

The widest of any phone. Stock apps include phone, messages, contacts, settings, photos, dispatch, banking, browser, services, garage, music. Third-party paid apps: dispatch (police/EMS), radio, dating, lifeinvader-clone, business management, courier, taxi, racing, weed-business — most premium scripts now ship with an lb-phone integration.

Our own devCon Lifeinvader (& lb-phone App) and devCon Garage (& lb-phone App) both ship native lb-phone apps as part of the install.

Performance

Idle resmon ~0.04 ms client-side. Active use spikes to 0.3-0.6 ms during heavy UI interactions (browsing photos, scrolling messages). Acceptable for any modern client.

gks-phone

What it is

Old guard. Originally released in 2018 by GKS, has been forked dozens of times. The "official" version is still sold on Tebex for around €30, but several community forks exist on GitHub for free.

Strengths

  • Cheapest viable option. Either free fork or one-time €30 for the legitimate version.
  • Massive existing integration base. Many older scripts have gks-phone hooks built in.
  • Lightweight. Lower resmon than lb-phone.
  • Open-ish. Community forks are full source — modify whatever you want.

Weaknesses

  • Feels old. The UI is recognizably 2018-era. Players coming from other servers will notice.
  • Original is abandoned. No updates since 2023. Forks are unmaintained or sporadically maintained.
  • Limited new-script integrations. Modern script vendors target lb-phone first, gks-phone last.
  • QBCore support is iffy. Original is ESX-only; QBCore forks have inconsistent stability.
  • Calls and messages work, but apps are ancient. The "Twitter clone" is unusable by 2026 standards.

Who should still use it

Servers under 30 players on a tight budget, or established servers that already have gks-phone deeply integrated and aren't willing to migrate. For anyone starting fresh: skip.

qs-smartphone

What it is

From Quasar Store — same team behind qs-inventory and other popular scripts. Released 2021, actively maintained. ~€50 one-time on the Quasar store.

Strengths

  • Polished UI. Looks great, closer to lb-phone than to gks.
  • Cheaper than lb-phone and includes major updates.
  • Tight Quasar ecosystem integration. If you run qs-inventory, qs-banking, qs-housing, the whole stack feels coherent.
  • Multi-framework (ESX + QBCore).

Weaknesses

  • Smaller third-party app ecosystem. Third-party devs target lb-phone first.
  • Quasar-locked. Best UX requires running other Quasar products. If you don't, you lose the integration advantage.
  • Less active development than lb-phone. Major updates ship every 8-12 months.
  • Smaller community means fewer free fixes and slower issue resolution.

Who should use it

Servers already invested in the Quasar ecosystem (qs-inventory, qs-banking). For those, qs-smartphone is the obvious choice.

qb-phone

What it is

Official QBCore phone, free, ships with the QBCore framework. Open source on GitHub.

Strengths

  • Free. No license, no fees.
  • QBCore-native. Zero integration effort if you're on QBCore.
  • Open source. Fork and modify freely.
  • Maintained by QBCore team — won't suddenly disappear.

Weaknesses

  • QBCore-only. Doesn't work on ESX or Ox Core without significant porting effort.
  • UI is functional, not exciting. Looks fine, doesn't wow anyone.
  • Third-party app ecosystem is small compared to lb-phone.
  • Performance is acceptable but not exceptional.

Who should use it

QBCore servers on tight budgets, or QBCore servers where the phone isn't a major focus. Most QBCore servers above 100 active players eventually migrate to lb-phone anyway.

yseries-phone

What it is

Newer entrant from the Project Sloth team, launched 2023. Paid (€60 one-time). Has built strong traction in EU RP circles in 2024-2025.

Strengths

  • Cleanest UI of all options. Designed by people who clearly care about visual polish.
  • Strong RP-server features. Built around RP use cases (group chats with crew-leader controls, anonymous messaging, evidence-friendly call logs).
  • Active development with frequent updates.
  • Good performance. Comparable to lb-phone, slightly lighter.

Weaknesses

  • Smaller third-party app ecosystem compared to lb-phone.
  • Less standardized integrations. Most premium scripts don't ship yseries-phone apps natively yet.
  • Smaller community means slower help on niche problems.

Who should use it

Servers prioritizing UI polish over app variety. Servers that don't need 15 third-party apps.

Feature matrix

Phone script comparison (mid-2026)
                    lb-phone   gks-phone   qs-smart   qb-phone   yseries
Price               €75         Free/€30    €50        Free       €60
Last updated        2026        2023        2026       2026       2026
Active dev          Yes         No          Yes        Yes        Yes
ESX support         Yes         Yes         Yes        Port       Yes
QBCore support      Yes         Iffy        Yes        Native     Yes
Ox Core support     Yes         No          Partial    No         Partial
3rd-party apps      ★★★★★      ★★★         ★★★        ★★         ★★★
UI polish           ★★★★★      ★★          ★★★★       ★★★        ★★★★★
Performance         ★★★★       ★★★★★      ★★★★       ★★★★       ★★★★
Community size      Huge        Large       Medium     Large      Small
Best for            Premium     Budget      Quasar     QBCore     Polish

The "I run [X], which phone?" cheat sheet

  • Running ESX, 50+ players, mid-budget: lb-phone
  • Running ESX, <30 players, tight budget: gks-phone fork (free)
  • Running QBCore, starter: qb-phone (free, built-in)
  • Running QBCore, 100+ players, willing to invest: lb-phone
  • Running Quasar inventory + banking: qs-smartphone
  • Running Ox Core: lb-phone (only one with full Ox support)
  • Want the prettiest possible phone: yseries-phone

Migration cost (if you're switching)

Phones are deeply integrated into other scripts (banking calls phone API, dispatch sends phone notifications, businesses use phone apps). Switching phones means:

  • Re-wiring every script that talks to the phone (10-30 scripts on a typical server)
  • Migrating player data (contacts, photos, message history) if the phone stores it in its own tables
  • Re-training your community on the new UI

Realistic migration time: 2-4 weeks for a competent dev. Don't underestimate.

The hidden cost: per-app pricing

Most phones (lb-phone, qs-smartphone, yseries) charge for premium apps separately. A typical premium phone setup ends up at:

  • Base phone: €60-75
  • Dispatch app (lb-dispatch or similar): €30-50
  • Radio app: €20-30
  • Business management app: €40-60
  • Lifeinvader / social app: €30-40

You're looking at €200-300 total to fully stock the phone. Plan for it.

What we recommend for devCon customers

For ~80% of our customers we recommend lb-phone as the platform, then choose individual apps based on actual server needs.

Our products with lb-phone apps built-in:

If you go the gks-phone or qs-smartphone route, our scripts still work — they just don't get the phone-app UI by default.

What's coming in 2026/2027

Things to watch:

  • lb-phone 3.x rumored to drop late 2026 — apparently a major UI overhaul plus an "AI assistant" feature. Speculative until released.
  • qs-smartphone 3.0 with full Ox Core support is in beta.
  • A new entrant from the Overextended team (ox_phone?) has been rumored for 18 months without official confirmation.

If something genuinely disruptive ships, it'll come from one of those three. Otherwise the 2026 landscape stays as described above.

Bringing it together

The phone is the most-used UI on any RP server. The right choice depends on your budget, your framework, and how deep you plan to integrate. For most servers in 2026, lb-phone is the safe premium pick. For everyone else, the alternatives are real and viable.

Whatever you pick, plan around the integrations: every other script that talks to the phone needs to be aware of which one you're running. Switching later is painful enough that getting it right up-front matters.

Related reading