FiveM · QBX · QBCore · ESX · standaloneFiveM phone script for QBX, QBCore, ESX, and standalone
One connected phone for your whole city.
The handset starts empty. A Cloud account keeps the player's data, a physical SIM keeps their number, and both outlive the device.
Cloud accounts and physical SIM cards carry a player's data and number between handsets. Custom apps plug in without touching the phone core. Runs on QBX, QBCore, ESX and standalone servers.1
Switch without starting over
A new phone. Not a fresh start.
Already using another FiveM phone? Source-specific migration tools can move compatible player data to Taintless Phone, including phone numbers, contacts, conversations, and other supported records.2
Review migration guidanceIdentity & continuity
Lose the handset. Keep everything.3
Phones start blank. A Cloud account carries the player's data, a physical SIM card carries their number, and both outlive any single handset.
Physical SIM cards.
Numbers that travel.
A phone number belongs to the character and lives on a SIM card item. Move the SIM to another phone and the number moves with it; messages and call history remain with the Cloud account.
Telecom dealer.
Lines sold in the city.
Players buy a new line and SIM at the in-city telecom dealer — an in-world interaction, not an admin command. Lost SIMs are reissued for the same number.
Stolen phone?
The old SIM stops working.
Reissuing a SIM invalidates the previous card immediately. The number remains with its owner, and the old handset loses access to the line.
Cloud account.
Sign in, and it is your phone.
Players create a handle and PIN during setup and remain signed in on that device. Signing in on a new phone restores the last device's Home Screen layout, wallpaper, and appearance settings.
Device lock.
Optional, PIN-protected.
Players can protect the device with a lock screen opened by their Cloud PIN. Without the PIN, a stolen handset stays locked.
One address.
Account and mailbox in one.
The Cloud address is also the player's mailbox — no separate mail account or password. Job and city mail reaches the same inbox on every phone the account signs into.
01Live demo
The real phone. Running in this page.
The build that ships to your server, rebuilt for the browser and filled with sample data. Tap the phone, open the apps, read a conversation, change a setting.
15 apps, included with both monthly and lifetime access.4
Tap the phone to start. About 5 MB the first time.
Custom Apps API v1
Custom apps. No core edits.
Register an app from a separate FiveM resource without editing the phone core, so phone updates do not overwrite its code. Set defaultApp to false in the registration manifest to list it in the in-phone App Marketplace for players to install.5
02Performance
Runtime cost, shown plainly.
Client time, memory use, and server time are reported separately, so you can judge the resource against the limits that matter to your server.6
- ms
- Client time
- KiB
- Client memory
- ms
- Server time
Current build reference profileNo active phone interaction
Results vary with server hardware, configuration, installed resources, and player activity.
- lighter on the client
- Up to 3×
- lighter on the server
- Up to 5×
- less client memory
- Up to 40%
- smaller download
- Up to 60%
Feature-heavy phone figures are published by its developer; Taintless figures are from the current local build. Memory readings are normalised to MiB. Hardware, configuration and test conditions may differ, so this is a reported-value comparison rather than a controlled benchmark.
03Implementation
Built for your server.Documented for your team.
Choose a view
Start with the integration. The resource detects supported frameworks at startup, keeps server settings in a readable configuration file, and exposes Custom Apps API v1 for apps that live outside the phone core.
Framework support.
Built in.
Stand aloneQBX, QBCore, and ESX are detected when the resource starts; standalone is also supported.
Custom apps require
core edits
Register the app from its own resource so phone updates do not overwrite its code.
No escrow.
Readable source.7
Review and adapt the supplied source for your entitled servers. The proprietary product licence still applies.
Custom Apps API.
Version 1.
Register apps against a versioned API without editing the phone core.
Server configuration.
One readable file.
Change the settings you need without a separate control panel.
Latest release.
Version 1.0.0.
2026-07-01
Dated releases with observable changes and required actions, collected in the changelog.
04Plans
One phone. Monthly flexibility or lifetime access.
Both plans include the same phone, included apps, and readable source files. Billing, update access, continued use, and gifting depend on the plan you choose.
Lifetime
No renewal£90one time
Billed once in GBP by Tebex.
Pay once and keep using delivered versions while the entitlement remains valid.
New releases are included while Taintless Phone remains actively maintained.
Monthly
£30/ month
Billed monthly in GBP by Tebex.
Lower upfront cost with access while your subscription remains active.
Renews monthly until cancelled; access ends after the paid billing period.
Current release: Early Access. The build is available now with the features described on this page and remains under active development. Review compatibility and installation requirements before purchase.
Lifetime or monthly?
Same phone, same apps, same source. Six things change with the plan: how you pay, what happens when payments stop, new releases, source access, server keys, and gifting.
Lifetime or monthly?
Same phone, same apps, same source. Six things change with the plan: how you pay, what happens when payments stop, new releases, source access, server keys, and gifting.
Billing
- Lifetime
- One payment of £90
- Monthly
- £30 each month until cancelled
Use after payments stop
- Lifetime
- Keep using delivered versions while the entitlement remains valid
- Monthly
- Access ends after the paid billing period
New releases
- Lifetime
- Included while the product is actively maintained
- Monthly
- Included while the subscription is active
Readable source
- Lifetime
- Included under the proprietary product licence
- Monthly
- Included during active access under the proprietary product licence
Server use
- Lifetime
- Custom Servers managed through server keys held by the receiving Cfx.re account
- Monthly
- Custom Servers managed through server keys held by the receiving Cfx.re account
Gift purchase
- Lifetime
- Available for another Cfx.re account
- Monthly
- Not available for recurring access
Prices are in GBP. Monthly access renews until cancelled, and Tebex confirms applicable taxes before payment. Refund policy · Product licence
Product information
Independent Product Notice
This FiveM phone system is independently developed and maintained by Taintless Studio and sold through Tebex as merchant of record. It is not approved, sponsored, or endorsed by Rockstar Games, Take-Two Interactive, or Cfx.re. FiveM and other third-party trademarks are the property of their respective owners.
How we approach platform use05Questions
Before you choose a plan.
Compatibility, migration, access, and delivery—answered before checkout.
Read the documentation- 1.QBX, QBCore, and ESX are detected when the resource starts. Standalone mode must be selected explicitly. A heavily modified framework may require a custom adapter or separate resource.
- 2.Migration coverage is source-specific. Supported records depend on the source phone, its version, and the apps enabled on the server. Run the migration against a private database copy, compare record counts, and resolve reported conflicts before scheduling the live cutover.
- 3.“Keep everything” refers to the account-backed data and SIM-linked number described in this section. The Cloud account retains conversations, mail, notes, photos, installed apps, and appearance backups; the physical SIM carries the number. Device-local state, including Clock data, remains tied to the handset.
- 4.Included apps share phone identity, but they do not all use the same storage model. Account-backed records follow the Cloud account, while Clock remains device-local. Custom apps own their durable data and business rules unless they deliberately connect them through phone identity or server exports.
- 5.Custom apps run from independently installed FiveM resources. Their UI is hosted in a sandboxed iframe, but privileged actions must be reauthorised by the app's server code; the iframe is not a security boundary. Setting defaultApp to false lists an already-running app in the App Marketplace and does not download code.
- 6.The idle and active figures are reference readings from the current local build, not guaranteed limits. Client time, server time, and client memory are reported separately. Hardware, configuration, installed resources, player activity, and test conditions can change the result; comparison figures are reported values rather than a controlled benchmark.
- 7.Readable source means the supplied files can be reviewed and adapted for permitted use on entitled Custom Servers. It does not make the product open source: sharing, resale, redistribution, and use outside the applicable entitlement and Creator Platform License Agreement (Creator PLA) remain prohibited.