Choose a free phone by its integration requirements before choosing its appearance. NPWD, EF-Phone and Z-Phone have different setup paths; none should be treated as a drop-in replacement for an existing phone database.
NPWD: use the built release
Project Error documents NPWD as framework-agnostic, with separate integration guidance for ESX and QBCore. Its installation guide points to the built npwd.zip release. The repository source ZIP is not the documented ready-to-install download. Check the selected release, voice dependencies and framework bridge together.
NPWD releases and installation guidance
NPWD installation documentation
EF-Phone: QBCore integration
The original EF Development repository targets QBCore. Its manifest loads qb-apartments configuration and oxmysql, while its README explains that a different garage needs integration work. Keep the resource folder named ef-phone and inspect the SQL before migrating existing player data. Do not delete your live phone tables to solve an empty app screen.
Z-Phone: identify the project and version
The Alfaben Z-Phone repository matches the showcase linked in the earlier article. Its source loads ox_lib and oxmysql; the README has separate framework notes. Other repositories also use the Z-Phone name, so record the exact owner and commit instead of mixing their features or installation steps.
Original Alfaben Z-Phone repository
A practical acceptance test
Back up phone records and test with two accounts. Check calls in both directions, messages after reconnecting, camera uploads, vehicle lookup and any money transfer. Reject duplicate payments, lost contacts or access to another character’s data. Repeat after a resource restart.
Measure resource time while performing the same actions on your own server. This comparison does not establish an idle-time ranking or promise that any phone is bug-free. Sources checked on 9 September 2026; in-game compatibility has not been tested here.