Oxide Tablet
Framework-agnostic tablet for FiveM — every item its own device with an IMEI, a customizable home screen, an App Store, notifications, and a shell other resources put their screens on.
oxide-tablet is a tablet players carry in their inventory, and a shell that other resources put their screens on. It ships with its own App Store, Settings and Maps apps, and any other resource that supports the tablet adds its interface as an app that appears on its own once both resources are running. Those resources never require the tablet — without it they keep using their own screens.
Every tablet item becomes its own device the first time it is used. It gets a 15-digit IMEI written into the item metadata and carries its own name, home screen, installed apps, player settings and battery charge when it changes hands. Players lay out up to 5 pages and a dock of 6 apps, drag apps and widgets where they want them, hide the rest in the App Library, and pick from 8 built-in wallpapers or images the server owner drops into the wallpapers/ folder. Apps post notifications that drop in as a banner while the tablet is open, collect in a tray under the status bar, badge the app icon, and pop up as a small bubble at the corner of the screen while the tablet is put away.
Server owners configure almost everything in game with /tablet settings, backed by the database rather than a config file, and can factory-reset any tablet by its IMEI. Developers get the tablet namespace in o-link on both sides, a host shim that mounts an existing NUI page as an app in a few lines, and a full guide for building apps and widgets. oxide-tablet is framework-agnostic through o-link and runs on QBCore, QBX and ESX.
Key Features
- Opens From an Item, a Key or a Command — A usable
tabletitem, a rebindable Open tablet keybind, or/tablet open. The item requirement is optional, and apps opened directly by another resource never need an item - Every Tablet Is Its Own Device — A 15-digit IMEI written into the item metadata (optionally shown in the item tooltip) that carries the tablet's name, home screen, installed apps and settings between owners
- Battery — Drains while the tablet is out and recharges while it is put away, at rates you set. A flat tablet won't open until it has charged. Switchable off entirely
- Held in Hand — A held pose and tablet prop that other players can see. The tablet closes itself on death, on going down, or when the item leaves the player's inventory
- Several Tablet Items — More than one item can open the tablet, and any item can be locked to a fixed list of apps for a work-issued device with no App Store
- Custom Home Screen — Up to 5 pages and a dock of up to 6 apps, drag-and-drop editing, an App Library for hidden apps, and per-tablet renaming
- Widgets — Built-in Calendar and ID widgets, plus widgets other resources add in small, medium and large sizes that open their app and carry its badge
- Wallpapers — Eight built-in presets plus any
png,jpg,jpegorwebpimage you place in thewallpapers/folder or point at overhttps:// - App Store — Players install the apps they qualify for on each tablet. Preinstall apps for everyone, or turn the store off so every available app installs itself
- Job, Gang and Duty Filters — The resource that registers an app decides who sees it
- Maps App — Owner-added public locations, the location blips each player already has on their game map, per-blip name and icon overrides, search, GPS waypoints and a drawn route, with separate mainland and Cayo Perico handling
- Settings App — Do Not Disturb, banners, sound and volume, per-app mutes, larger text, bold text, reduced motion, renaming, and layout or settings resets
- Notifications — Banners, a tray under the status bar, app badge counts, a configurable store limit and on-screen time, and a notification sound you can replace
- Bubbles While Put Away — A small card at the corner of the screen when a notification arrives and the tablet is away, with a per-app opt-out
- Live Settings Editor —
/tablet settingsedits nearly every setting in game, stored in the database, most applying with no restart - Admin Tools — Factory-reset any tablet by IMEI (
/tablet wipe) and post test notifications (/tablet notify), plus/tablet deviceand/tablet resethomefor players - Everything Persists — Layouts, installs and player settings are saved with the tablet item, or with the character when no item is involved, and survive a restart
- Developer API — The
o-linktabletnamespace on both sides for registering apps, widgets and notifications, so consuming resources never depend on the tablet directly - Framework-Agnostic — QBCore, QBX and ESX through
o-link, with model swaps for game builds missing the tablet prop, and an English locale (locales/en.json) covering every notification, command, screen and app
Requirements
Required
| Resource | Purpose |
|---|---|
o-link (1.8.0 or newer) | Framework abstraction for the inventory, jobs and gangs, admin checks, notifications, callbacks, logging and the map data behind the Maps app |
ox_lib | Locale files and shared utilities |
oxmysql | Device, home-screen and live-settings persistence |
An inventory o-link supports | Finds the tablet item and stores its IMEI in the item's metadata |
Optional
| Resource | Purpose |
|---|---|
| Resources with tablet support | Register their own apps and widgets on the tablet |
The tablet ships with three apps of its own: App Store, Settings and Maps. Everything else on it comes from other resources you run. When both are running, their app shows up in the App Store on its own — there is nothing to set up in the tablet.
Supported Frameworks
| Framework | Support |
|---|---|
QBCore (qb-core) | Full |
QBX (qbx_core) | Full |
ESX (es_extended) | Full, with a supported inventory |
| Custom | Via o-link |
Quick Start
Install ox_lib, oxmysql and o-link 1.8.0 or newer, plus an inventory o-link supports (such as ox_inventory or qb-inventory).
Place oxide-tablet in your resources folder and start it after o-link:
ensure o-link
ensure oxide-tabletSet up the tablet item — it must be usable and must not stack. The exact lines for QBCore, QBX and ESX are in Installation → Framework Setup.
Review shared/config.lua before the first start, then start the server. The database tables are created for you.
Use the tablet item in game, and run /tablet settings as an admin to manage everything live.
See the Installation Guide for the full setup flow.
Settings are stored in the database after the first start
On its first start the tablet copies shared/config.lua into the shared oxide_settings table. From then on the database copy is used, so editing the file does nothing — change settings in game with /tablet settings. See Configuration → How Settings Work.
Documentation
Installation
Prerequisites, load order, the tablet item for each framework, and verification.
Configuration
Every setting, its default, and how database-backed settings work.
Features
Home screen, widgets, App Store, notifications, devices and battery.
Maps App
Locations, detected blips, overrides, waypoints and the route overlay.
Settings App
What players can change on their own tablet, and where it is saved.
Admin Tools
Every /tablet command, the settings editor, and permissions.
API Reference
The olink.tablet API, events, hosted page messages and widget data shapes.
Building Apps and Widgets
Step-by-step developer guide with a complete example resource.
Troubleshooting
Common issues and fixes.