FiveM character creation: face settings, saving and presets

Use the creator your community actually provides

There is no single character-creation menu shared by every FiveM server. Ask which appearance resource the community uses and where new characters enter it. Existing characters may use a different barber, surgeon or clothing workflow, with different permissions or prices.

The concrete menu example here is Illenium Appearance v5.7.0, reviewed at commit 1b003ec169b15f145d519438ba7c6454bf746f27. The workflow below is a way to record and compare settings; Magnate has not created or photographed a character in this resource.

Choose the model before copying a face recipe

For either a male or female character, begin with the model that your server supports for that creation path. Record its identifier in your worksheet. A recipe made for another model or a custom appearance package is not automatically transferable.

When following a creator’s tutorial, ask for the resource/version and actual settings, not just a portrait. Lighting, camera distance, pose and overlays can make two views of the same settings look different. Compare front and side views under consistent conditions.

Choose an appearance direction before tuning every slider: for example, the desired face outline, nose profile and brow. Those are visual goals, not a claim that one recipe is objectively the best male or female character.

Work through inheritance, features and overlays in order

The reviewed English locale groups the creator into Inheritance, Face Features and Appearance, alongside model and clothing sections. Inheritance includes face and skin parent selections and mix controls. Face Features includes nose, brows, cheeks, eyes/mouth, jaw, chin and neck controls.

Appearance labels include hair, beard, makeup, complexion and eye color. These labels identify categories in this revision; availability depends on the server’s configuration and the selected model.

Use the downloadable character settings worksheet

The CSV is a blank recording template, not an import code or a ready-made attractive character. Fill in the exact labels and values displayed by your server. It includes environment, model, inheritance, face-feature, overlay and save-check rows.

Keep one sheet per character recipe and note the date. Add front/profile screenshot references if you have your own images. If your menu combines or renames a field, record its actual label instead of guessing a numeric conversion.

For a reproducible male or female appearance, record the complete baseline before making a second version. Change one group at a time and compare under the same lighting. Do not overwrite the only record of a result you want to keep.

Download the character settings worksheet (CSV)

Why an outfit code may not reproduce a face

In this pinned Illenium client, the save-outfit path gathers the ped model, clothing components and props. Its new-character customization path instead submits an appearance result to the save-appearance flow. These are different payloads and workflows.

Do not assume an outfit code contains inheritance, face sliders or overlays merely because it changes clothing successfully. Use the outfit-code guide for the reviewed sharing behavior. For full-face sharing in another resource, require documentation for that exact feature and format.

This page does not publish invented character preset codes or promise cross-server imports. If your community provides its own face-preset feature, follow its supported sharing method and check the required assets and model before applying someone else’s recipe.

Check saving separately from the preview

The reviewed Illenium new-character configuration selects available sections through Config.NewCharacterSections. A missing face tab can therefore be an enabled-section or integration question. Changing a clothing keybind cannot create a section the server has not exposed.

After using the normal save action, check the result through the supported return-to-game and reconnect path. If the appearance looks correct only in the editor, report that exact distinction to the owner. A preview is not proof that the server saved and restored the same data.

Owners should test with a synthetic staging character: initial creation, appearance submission, spawn handoff and reconnect. Keep the selector and appearance versions in the report. Do not delete a live character as a shortcut for diagnosing a save or load failure.

Troubleshoot the visible difference first

If the face differs immediately, compare the model and inheritance before changing overlays. If only hair or makeup differs, compare those fields and the installed assets. If everything changes after reconnect, investigate the save-and-restore path rather than repeatedly rebuilding the recipe.

Record expected and observed settings, the last completed step and a redacted error excerpt. Keep credentials and private player data out of public screenshots. This GTA V/FiveM workflow is not evidence of GTA VI character-creation features or asset compatibility.

Questions, answered.