Optimize assets

Start here

Run Optimize assets on a copy of your source files

1. 1

   Open the workflow: PulseConvert → Optimize. If the tool is locked, check its access notice instead of assuming it is available to your account.

2. 2

   Prepare the exact kind of input listed for this feature: A supported resource or asset to optimize. Keep an unchanged backup and ensure you have permission to reuse the assets.

3. 3

   Open the tool page and provide the requested source files and any displayed options. Check that the detected file types match the input requirement; do not replace unrelated files just to make an upload succeed.

4. 4

   Review the resulting files or job details. Expected outcome: Optimized output and the job's processing/warning information.

5. 5

   Compare the result with your original in a local editor. For resources that load in FiveM, start with an isolated test server; inspect the first client/server console error and test the asset in game before installing it for players.

Before you begin

• A supported resource or asset to optimize.
• Signed-in access may be required for upload and job history.

Overview of the setup

1. 1

   Prepare

   Keep an original copy. Input: A supported resource or asset to optimize.

2. 2

   Process

   Open the workflow and supply the source. Choose the appropriate asset category and compare visual quality, file size and resource behavior against the original.

3. 3

   Verify and install

   Review the job log and warnings; expect Optimized output and the job's processing/warning information. Test the resulting resource on a nonproduction FiveM server.

Features explained

What each feature does and what to check before publishing or installing the result.

If it still does not work

1. If the tool rejects the input, compare your file extension and the files inside the archive to the input requirement above. Source files inside nested folders may need extra review.
2. If the tool reports success but the result does not function, do not assume the file is compatible: inspect warnings, actual output names and their references, manifest files, and version compatibility.
3. Review warnings and test the output before putting it on a live FiveM server.

Troubleshooting and safety checks

• Check input files, supported formats and processing warnings before retrying.
• If FiveM fails to start the resource, review the first console error and verify generated paths and metadata.