Pedify guide
Install and check an exported FiveM resource
Use the files and folder shown in the exported package. Test one copy on a private server before replacing anything in a live resource.
Choose the resource export
In Review export, choose the standalone Resource option when you want a complete resource ZIP. Keep the downloaded ZIP untouched as your backup. A stream files only export has no standalone resource name or manifest; add those files to an existing resource only if you can also register any included metadata there.
Keep the exported folder layout
Extract the ZIP under the server’s resources directory. Follow its archive paths exactly: the resource folder must contain fxmanifest.lua at its root, with the exported stream files and any metadata files in the paths referenced by that manifest. Do not wrap the folder in an extra directory or move only the visible model file.
Use the resource folder name shown by the export summary. Add ensure <resource-name> to your server’s existing server.cfg. FiveM documents the manifest format in the Cfx.re resource manifest reference and the ensure command in its server command reference.
Start a private test and check the model
- Start the test server and inspect its console for a missing resource, manifest or metadata error.
- Use the exact ped or model name shown in the export summary with a menu that is already approved on that server.
- Check the result in game on a clean client. For clothing, confirm that the intended base ped and collection are selected, then try the available variations.
- Restart just the test resource using your server’s normal controls, spawn or select the model again, and repeat the visible checks. Test a second client only if your server setup needs networked visibility.
The package contents and a successful server start do not establish every model behavior, menu permission or gameplay outcome.
Updating an existing resource
Make a backup copy first. Compare the exported filenames and metadata with the existing resource. Copy only the files that belong in that resource’s established layout, keep its manifest and metadata references consistent, and repeat the private test before replacing the live copy.
Pedify’s export-check guide explains missing companion files. For a changing estimate, use the server’s cost estimator.