Visual identity / article 41

Make them
recognisable.

“Change the face” can mean three different data jobs. Separate editable appearance values, a specific Head Asset and a tattoo option before touching the player—then prove the 3D result after both saves.

VISUAL ROUTERLOOK COMPONENT VALUES→HEAD ASSET REFERENCE→INK BUILT-IN OPTION→PROOF MATCH CLOSE-UP

01 / DIRECT ANSWER

How do you change a player’s appearance, head model or tattoos?

Back up the Career, stay outside FC’s own Edit Player screen, then press F9 → Features → Players, open the intended player and choose Appearance or Accessories. For a specific head on an eligible non-created player, set Has HQ. Head to Yes, Head Class to Specific and Head Asset ID to the target player ID. For tattoos, use the current option picker instead of guessing raw codes. Apply Changes, use Player → Save, re-enter the FC screen, Career Save, then inspect the 3D player in a match.

ORDINARY LOOKEdit values

Record originals and change the smallest meaningful component batch.

appearance / accessories
ANOTHER SPECIFIC HEADPoint to an asset

Three fields must agree. A created player is a documented stop.

HQ + Specific + ID
BODY ARTUse the picker

v26.3.5 replaced the worst random-code workflow with options.

verify visible zone

02 / OBJECT CLASSIFIER

One player, three visual layers, three different contracts

The creator documents appearance/accessory editing broadly, an exact Head Model recipe narrowly, and a later tattoo-picker improvement. Treating all three as “face IDs” creates bad saves and impossible expectations.

01COMPONENT LOOK
Appearance & accessories

Hair, facial hair, skin/body values, kit fit, socks, boots and visible gear.

EDIT SMALL BATCHES
02ASSET REFERENCE
Specific head model

A three-field pointer to an eligible player/head asset—not a face sculptor.

ELIGIBILITY FIRST
03BUILT-IN ART
Tattoo option

An existing game asset selected from current fields and verified on the body.

PICKER FIRST

WHY THIS MATTERSCareer players want authored identity, not “fifty cloned faces.” Current community threads repeatedly ask for distinct academy hair, heads, tattoos and accessories. The job is creative; the procedure must still remain attributable and reversible.

03 / INTERACTIVE APPEARANCE LAB

Plan the layer and reveal its real stop conditions

Select the visual job, record only the intended batch and test the player’s origin before using a Head Asset. This browser tool does not inspect FC 26, resolve an asset, render a face or perform a save.

APPEARANCE LAB / LOCAL PLANNERClassify the visual layer first

No game connection or asset preview

01 / COMPONENT VALUES

Choose the smallest visual batch

01/04

These are planning families, not an exhaustive field schema. Use the labels exposed by your current mapped build and capture every original value before editing.

SCAN LIMIT

A specific/HQ scan is not the same as a component-built generic face. If hair or facial parts are unavailable, do not convert the head blindly; first identify the head class.

04 / APPEARANCE & ACCESSORIES

Change a component-built look in small, named batches

The official README confirms appearance and accessories but does not publish an exhaustive current field schema. Current visual evidence shows hair, facial hair, skin/body values, socks and accessories; use the labels in your mapped build as the final UI truth.

FACE / HAIRComponent identity

Hair, beard, skin and facial values are useful for generic/component-built players. A specific scan may not expose the same controls.

close-up proof
BODYSilhouette

Height and body-related fields can affect both identity and gameplay presentation. Never guess the original values.

match proof
KITWear state

Kit fit and Sock Style belong to the visible player presentation. Sock Style is explicitly documented from v26.3.1.

full-body proof
GEARAccessories

Boots, sleeves, masks and other visible gear can distinguish a prospect without replacing the underlying head.

fixture proof
FIELD-LIST LIMIT

Video demonstrations are observations, not an official complete schema. If a label is absent from your current Player Editor, stop and check the FC build ↔ Live Editor mapping; do not copy a legacy tutorial’s raw value into Game Database.

05 / EXACT HEAD MODEL RECIPE

A specific head works only when all three fields agree

The Wiki says Head Model IDs equal player IDs. On an eligible player, use the FC 26 ID sheet linked by the Wiki, set the complete triple and confirm the result in Squad Hub or Transfer Hub. This is an asset reference—not a custom face editor.

ASSIGN SPECIFIC HEAD3 → 1
  1. 01
    HAS HQ. HEADYes
  2. 02
    HEAD CLASSSpecific
  3. 03
    HEAD ASSET IDTarget player ID
Apply Changes → Player Save → verify
REMOVE SPECIFIC HEAD3 → 0
  1. 01
    HAS HQ. HEADNo
  2. 02
    HEAD CLASSGeneric
  3. 03
    HEAD ASSET ID0
Apply Changes → Player Save → verify
!
Created player? Stop here.

The official Wiki says this Head Model method will not work for a created player. A video about FC’s built-in face import, Clubs, a generic youth code or a face mod does not remove that documented limit.

ID sanity check: record source player, target player, target ID, Head Class and whether the target asset is present in the currently installed game/mod set. The Wiki’s Messi example uses 158023; it is an example, not a universal test asset.

06 / TATTOO OPTIONS

The current first choice is a picker, not a random-number marathon

Live Editor v26.3.5 added an option picker for Tattoos. Choose from the current Player Editor, change one field at a time and verify the corresponding body area in a match. A raw ID may exist without being a useful, visible or compatible choice for that player and installed asset set.

01 / SELECTCurrent option

Use the picker exposed by the current mapped Live Editor build.

→
02 / RECORDOld + new value

Keep the exact field, resolved label/value and player ID together.

→
03 / INSPECTCorrect body area

Use a match camera or replay where the intended area is visible.

COMMUNITY SHORTCUTGame Database → Tattoos

A community reply recommends filtering the Tattoos table by location. That can help advanced inspection, but it is not creator documentation or a visual preview guarantee.

OFFICIAL CODE EXAMPLELeft-arm Lua mapping

The creator repository includes a scripted mapping example. It proves a field/value relationship, not a complete current catalog.

THIRD-PARTY PACKDifferent asset contract

A custom tattoo pack has its own installation, IDs and title-update compatibility. Built-in picker behavior does not validate it.

07 / DO NOT CONFLATE

Head Asset, Head Variation and miniface are not synonyms

Search results collapse several tools into “import face.” Use the output surface and owner to identify the job before following any tutorial.

TERMWHAT IT CHANGESOWNER / PROOF
Appearance components

Editable 3D values such as hair/body/accessory fields

Player Editor labels → close-up/match
Head Asset ID

Which specific 3D head asset the player references

Live Editor triple → Hub + match
Head Variation

A variant provided for the same ID by an installed face mod

Face-mod author → mod-specific proof
Miniface

The 2D portrait shown in menus and lists

Import/Generate workflow → menu portrait
FC face import

A sculpted/created head in FC’s built-in creator

Base-game creator → different surface
PUBLISHED / ARTICLE 42Need the menu portrait—not the 3D head?Miniface import & generation →

08 / SAVE & PROOF CHAIN

A visible edit is not durable until the Career owns it

  1. 01
    Create a rollback slot

    Save the Career to another slot and capture the player ID, origin and every field you will touch.

    BACKUP
  2. 02
    Leave FC Edit Player

    Use Squad Hub, Central or Office. Closing FC’s own Edit Player screen can overwrite Live Editor data.

    CONTEXT
  3. 03
    Open the exact object

    F9 → Features → Players → find by identity → Edit. Confirm you did not select a namesake or clone.

    PLAYER
  4. 04
    Change one visual layer

    Appearance batch, complete Head Model triple or one tattoo field—not all three at once.

    ATTRIBUTION
  5. 05
    Apply and save the entity

    Use Apply Changes where exposed, then Player → Save in the top-left menu.

    ENTITY
  6. 06
    Refresh and persist

    Exit/re-enter the current FC screen, inspect the result and Career Save to the test slot.

    CAREER
  7. 07
    Prove the 3D surface

    Use Squad/Transfer Hub for the head, then a match close-up for hair, gear, body art and the final model.

    PROOF
CAREERPlayer Save → Career Save

Use a separate test slot until the 3D result survives reload.

SQUAD FILESave Squads separately

Customize → Profiles → Save Squads; later Load Squads and choose Use Current Squads.

09 / HARD BOUNDARIES

What this visual editor does not promise

CREATED PLAYERNo Head Model recipe

The current Wiki explicitly excludes the created-player object.

GENERIC FACENo universal 46xxxx recipe

Community reverse engineering has exceptions and is not creator documentation.

SPECIFIC SCANNo component parity

A scanned head may not expose generic hair/facial controls.

HEAD VARIATIONNo built-in catalog promise

Variants can depend on an installed third-party face mod.

MINIFACENo automatic portrait sync

The 2D menu image is a separate object and workflow.

PLATFORM / ONLINEPC offline only

No console route; FUT, Clubs and Volta are outside the creator’s scope.

10 / ROLLBACK TICKET

Restore the entire visual contract, not just the ID

A safe undo restores the field family that changed, repeats the same save chain and verifies the same surface. For a Head Model, all three fields are one atomic recipe.

CAPTURE BEFOREPlayer + values
  • Player ID and origin
  • Head HQ/Class/Asset triple
  • Appearance fields touched
  • Tattoo field and value
→
RESTOREOriginal layer
  • Restore the complete triple
  • Do not guess a “default” ID
  • Apply Changes
  • Player → Save
→
PROVE AGAINSame surfaces
  • Refresh Hub
  • Career Save/load
  • Match close-up
  • Keep rollback slot
NO SECOND SLOT?Build the Career backup before visual experiments→

11 / FRESH VIDEO AUDIT

Twenty-eight results, but no complete current proof chain

Three exact-intent searches on 17 August 2026 mixed current Live Editor overviews, FC 24/25, FC’s built-in creator, face-mod installation, Head Variation, tattoo packs and short metadata-only clips. The current Wiki controls the Head Model procedure.

V12Useful visual scope

Current captions show appearance/accessory jobs, but “any player” head-scan language conflicts with the Wiki’s created-player stop.

V19Head-class context

Current observation separates generic hair editing from some scanned faces; not an exact recipe.

VARHead Variation result

Current metadata concerns variants for one installed face-mod ID—not assigning another Head Asset.

NEWFace-import transcript

V153 was normalized locally and confirmed a base-game creator surface, not Live Editor.

VIDEO EVIDENCE LIMIT

No current caption-backed result completed HQ = Yes → Class = Specific → Asset ID, a created-player negative control, Player/Career saves and in-match validation. Tutorials remain context; creator documentation remains authority.

12 / FAQ

Appearance, head-model and tattoo questions

01How do I change a player appearance in FC 26 Live Editor?

Back up the Career, stay outside FC’s own Edit Player screen, then press F9 → Features → Players, open the intended player and use Appearance or Accessories. Record the old values, change a small batch, Apply Changes, use Player → Save, refresh the FC screen and save the Career.

02How do I give a player another player’s head model?

For an eligible non-created player, open Appearance and set Has HQ. Head to Yes, Head Class to Specific and Head Asset ID to the target player ID. Apply Changes, use Player → Save, then confirm in Squad Hub or Transfer Hub and in a match.

03Are Head Model IDs the same as player IDs?

Yes, that is the current official Wiki instruction. Use the FC 26 ID spreadsheet linked by the Wiki and verify that the target asset exists in your installed game/mod state.

04Can I use the Head Model method on a created player?

No. The official Wiki explicitly says the Head Model replacement will not work for a created player. Do not force the three fields or treat a face-import video from FC’s creator as proof otherwise.

05How do I remove a custom head model?

In Appearance, set Has HQ. Head to No, Head Class to Generic and Head Asset ID to 0. Apply Changes, Player → Save, refresh the FC screen, Career Save and confirm the generic result.

06How do I add tattoos without guessing codes?

Use the Tattoo option picker added in Live Editor v26.3.5. Change one tattoo field at a time, record the original and selected value, save through the full chain, and inspect the visible body area in a match.

07Why can I not change the hair on a scanned face?

A specific/HQ head is an asset, not necessarily a component-built generic face. Current video evidence observes that some scanned heads do not expose the same hair editing behavior. Record the head class and avoid converting fields blindly.

08Is Head Variation the same as Head Asset ID?

No. Head Asset ID selects the head asset referenced by the player. Head Variation usually selects another version supplied for that same ID by an installed face mod. Availability and valid values belong to that mod’s documentation.

09Does changing the head also update the miniface?

No automatic relationship is documented. The miniface is the 2D menu portrait and has its own import/generate workflow; the Head Model is the 3D player head.

10Can I use Live Editor appearance changes on console or online modes?

No supported route is documented. FC 26 Live Editor is a Windows PC injection tool for offline use, and the creator excludes FUT, Pro Clubs and Volta.

13 / EVIDENCE LEDGER

The Wiki controls eligibility; the changelog controls current UI additions

01
Official Editing Player Wiki

Primary Head Model assign/remove recipe, created-player stop, Player Save, screen refresh, Career/Squads persistence and mode limits.

↗
02
Official FC 26 changelog

Sock Style added in v26.3.1 and the Tattoo option picker added in v26.3.5.

↗
03
Official project README

Player Editor appearance/accessory scope, Windows PC product identity and offline-only boundary.

↗
04
Official Head Asset Lua example

Advanced corroboration of the HQ-head, head-class and head-asset field relationship; the UI is the normal one-player route.

↗
05
Official tattoo Lua example

Advanced left-arm tattoo mapping example; not treated as a complete visual catalog.

↗
06
FC 26 player/head ID sheet

Current ID resource linked directly by the creator Wiki for Head Asset targets.

↗
07
Audience: FC 26 tattoo codes

Real academy-customization intent, random-ID pain and community database-table language; no product authority.

↗
08
Audience: youth face customization

Shows generic-face confusion and unresolved community reverse engineering; not promoted as a supported recipe.

↗
09
Audience: player accessories

Current demand for distinct academy faces, hair, body and accessories, including the PC/console divide.

↗
10
V12 — current appearance overview

Caption-backed examples of appearance/accessory jobs; its broad head-scan claim is narrowed by the official created-player warning.

↗
11
V19 — current Player Editor context

Observed generic-versus-scanned hair behavior; not an exact Head Model or tattoo procedure.

↗
12
Head Variation result

Current metadata-only example of a mod-specific Head Variation task, kept separate from Head Asset assignment.

↗
13
Built-in face-import boundary

Newly normalized current captions cover FC Create Player face import, a different surface from Live Editor.

↗
14
V152 — fresh exact-topic audit

28 returned results across three searches; no current caption-backed video completed the official three-field recipe and proof chain.

↗
RESEARCH FREEZE · 17 AUGUST 2026

The official Wiki supplies the Head Model fields, created-player stop and save chain; the README/changelog supply feature and version scope. No licensed current fixture was available for an independent appearance/head/tattoo save test. Community sources define user language only. Wiki screenshots may retain older visual chrome.

NEXT PUBLISHED GUIDE / ARTICLE 42Import or generate a miniface42 →