LB Phone vs Quasar Smartphone vs GCPhone: Which Phone Fits Your Server?
By Luke, RPScripts
Short answer
For most ESX, QBCore and QBOX servers we recommend LB Phone. It names the widest range of frameworks in our sources, its required dependencies are short (oxmysql plus your framework), and it documents the integrations servers usually need: unique phone items, custom frameworks, housing, uploads and video calls. Quasar Smartphone is a good fit if your server already runs Quasar resources. GCPhone only makes sense for old ESX 1.1 or 1.2 servers that accept unmaintained code.
A phone touches calls, character data, inventory items and services like banking or dispatch, so we compare documented requirements and integrations, not app counts. A long app list does not establish that those apps work with your existing resources. This is a comparison of documentation, not a hands-on performance test.
The three phones at a glance
- LB Phone (v2) is a full smartphone for FiveM with automatic framework detection and a separate phone prop resource.
- Quasar Smartphone is a commercial phone from Quasar Store. The current line is Smartphone 2026, documented as Smartphone V3.
- GCPhone is an older open project. The original N3MTV repository points to the Re-Ignited Phone continuation.
Comparison table
"Not documented" means we did not find it in the sources we checked. It does not mean the feature is missing.
| LB Phone v2 | Quasar Smartphone V3 | GCPhone / Re-Ignited | |
|---|---|---|---|
| Frameworks | ESX, QBCore, QBOX, ox_core, vRP 2.0, standalone; auto-detect | ESX, QBCore, Qbox; vRP experimental; standalone without a framework; auto-detect | Separate ESX 1.1 and ESX 1.2 archives; QBCore/Qbox support not established |
| Database | MariaDB 10.11+, oxmysql | MariaDB 10.6+, oxmysql | mysql-async |
| Other requirements | loaf_bcrypt recommended; current artifacts; OneSync Infinity optional (needed for AirShare) | ox_lib, xsound (or qs-3dsound / mx-surround), smartphone-prop, OneSync required; voice resource for calls, pma-voice recommended | screenshot-basic for photos, or disable photos |
| Unique phone numbers per item | Yes, with a metadata inventory; ox and qb recommended, lj, core and qs supported, custom guide for others | Yes, a metadata inventory gives every phone item its own number | Not documented in our sources |
| Media uploads | Fivemanage by default; own S3/R2 via lb-presigned | FiveManage, FiveMesh, BasiX or your own host | screenshot-basic |
| Video calls | WebRTC; TURN via Cloudflare (built in) or Metered | TURN server required for video; Cloudflare or Metered | Re-Ignited disables WebRTC calling for its OneSync setup |
| Custom framework | Documented: editable standalone framework files with client and server guides | Not documented in our sources | Not documented in our sources |
| Latest release | Not stated in our sources; updates come with patch notes | Smartphone 2026 / V3 | gcPhone 2.21 (April 2019), Re-Ignited V1.5 (December 2020) |
| Where to get it | RPScripts: $49.00 list price on 30 Oct 2026; instant download; newer files in account downloads | Creator store; linked to your Cfx.re Portal account after purchase. Check the current price with the creator | Free public GitHub releases; GitHub shows no licence for either repository |
| Data converter between them | Not documented | Not documented | Not documented |
Why we recommend LB Phone for most servers
1. It runs on more frameworks without extra work. The product page names ESX, QBCore, QBOX, ox_core, vRP 2.0 and standalone, with auto-detection by default. Quasar V3 covers ESX, QBCore and Qbox and lists vRP as experimental. If you ever change framework, LB Phone is the option in this comparison that names the most targets, and a custom framework has its own documented route.
2. Fewer hard requirements. LB Phone needs oxmysql and your framework. OneSync Infinity is optional and only needed for a few features such as AirShare, and loaf_bcrypt is recommended, not required. Quasar V3 additionally requires ox_lib, xsound, its prop resource and OneSync. One honest trade-off: LB Phone asks for MariaDB 10.11 or newer, Quasar for 10.6 or newer.
3. The integrations are documented. Unique phones work with five named inventories plus a custom-inventory guide. The home app supports qb-houses, loaf_housing and qs-housing by default, with a guide for others. Video calls have built-in Cloudflare TURN support. Developers get a documented list of server exports, for example to send messages, add contacts or push emergency notifications from job scripts. You can add your own apps through Config.CustomApps or the custom app exports.
4. It is maintained with clear update steps. The creator documents an update routine with backups and patch notes, and publishes database update queries when a release adds columns.
5. Buying on RPScripts is straightforward. LB Phone v2 is listed at $49.00 (30 Oct 2026) with an instant download after payment. Newer files appear in your account downloads, support covers download access and product-specific setup questions, and a 30-day technical guarantee refunds the purchase if it does not work as described and support cannot fix it. The guarantee does not cover a change of mind.
Get LB Phone v2 on RPScripts: instant download, updates in your account and a 30-day technical guarantee.
Quasar Smartphone: strong if you already run Quasar
Quasar's current line is Smartphone 2026, documented as V3. On its product page the creator advertises 50+ apps, 18 free DLC apps, 45 languages and four phone models, two of them foldable. The package is linked to your Cfx.re Portal account after purchase.
V3 requires MariaDB 10.6 or newer, oxmysql, ox_lib, xsound (or qs-3dsound / mx-surround if they run), its smartphone-prop resource and OneSync. Calls need a voice resource; pma-voice is recommended and other Mumble-based systems also work. Media uploads can use FiveManage, FiveMesh, BasiX or your own host, and video calls need a TURN server from Cloudflare or Metered. Free Smartphone DLCs require the supported base phone, and some apps depend on separate Quasar resources such as the associated racing or motel system.
Keep V3 separate from the older Smartphone PRO line; do not assume an app, voice adapter or add-on from one edition is part of another. RPScripts lists the legacy PRO build as QS Smartphone (Legacy 1.7.96). It requires ox_lib, oxmysql, xsound and mhacking plus game build 2545 or newer, and it is not V3.
GCPhone and Re-Ignited: only for legacy ESX
The latest published releases are gcPhone 2.21 from April 2019 and Re-Ignited V1.5 from December 2020. Re-Ignited offers separate archives for ESX 1.1 and ESX 1.2; its instructions do not establish QBCore or Qbox support. Start mysql-async and the matching framework first, then gcphone before job resources.
The included base.sql adds a phone_number column to users and creates the tables phone_app_chat, phone_calls, phone_messages and phone_users_contacts; two of them use MyISAM. The column addition is not guarded against an existing column. The continuation disables WebRTC calling for its OneSync setup and needs screenshot-basic for photos. It costs nothing, but you maintain it yourself.
Which phone fits which server?
- Most ESX, QBCore or QBOX servers: LB Phone. Broad framework support, short requirement list, documented integrations and updates through your RPScripts account.
- ox_core, vRP 2.0, standalone or a custom framework: LB Phone. It names ox_core and vRP 2.0 and documents a custom-framework route. Quasar lists vRP as experimental.
- You already run several Quasar resources or want Quasar's DLC apps: Quasar V3 may fit better, because those apps depend on the Quasar base phone and related Quasar resources.
- Your host cannot run MariaDB 10.11: LB Phone needs 10.11 or newer; Quasar V3 accepts 10.6 or newer. For game-panel hosts with outdated MariaDB, the LB docs suggest contacting your host or, preferably, moving to a VPS.
- Old ESX 1.1 or 1.2 server with no budget: Re-Ignited targets these versions, but its last release is from December 2020.
For any phone, confirm that the exact release supports your GTA V edition. The Cfx.re migration notes list Mumble as deprecated on Enhanced, so a voice dependency alone does not prove that calls work there. A missing framework badge is not proof of compatibility either.
Ready to switch? Get LB Phone v2.
Test before you switch
Run only one phone at a time. Quasar's own guide says to remove every other phone first, naming lb-phone among others, because these phones use the same item, keys and events. Then test with two ordinary characters on a separate server: calls (answer, decline, mute, reconnect), messages with attachments across a restart, handing over a unique phone, bank transfers with enough and too little money, and job apps with authorized and unauthorized characters.
If you are moving from GCPhone, note that LB Phone's installation guide says to delete all tables starting with phone_ before running its SQL file, and gcPhone's own tables use that prefix. Back up and plan the move first; our migration guide covers the steps.
FAQ
Which phone do you recommend?
For most ESX, QBCore and QBOX servers, LB Phone, because of its framework coverage, short requirement list and documented integrations. If you already run Quasar resources, Quasar V3 can be the better match.
Does LB Phone support QBOX?
Yes. The product page lists QBOX alongside ESX, QBCore, ox_core, vRP 2.0 and standalone.
Which MariaDB version do LB Phone and Quasar need?
LB Phone needs 10.11 or newer, Quasar V3 needs 10.6 or newer.
Do both support a unique number per phone item?
Yes. Both document it with an inventory that supports metadata.
Does GCPhone work on QBCore?
The Re-Ignited instructions do not establish QBCore or Qbox support.
Can I move my existing phone data from one to another?
None of our sources documents a converter between these three phones. Plan a custom conversion or a clearly communicated fresh start.