PostProcessors

Processor subclasses that run after a third-party package has been imported into the project. They modify imported assets in-place — renaming FBX nodes and animation clips, upgrading materials to URP, and stripping metadata from local packages.

Architecture

Data Flow

Execution Order

PostProcessors run in this order (defined in ThirdPartyPackageProcessor):

1. FBXProcessor — renames FBX internals before other processing

2. MaterialProcessor — upgrades materials to URP

3. MetaProcessor — strips metadata from local packages

Processors

Processor	File Filter	ProcessorTable Contexts	Description
FBXProcessor	.fbx	MESHES, MATERIALS, ANIMATIONS	Renames FBX nodes, materials, and animation clips
MaterialProcessor	.mat	—	Upgrades Standard shader materials to URP/Lit
MetaProcessor	all (local only)	—	Strips AssetOrigin from .meta files

All PostProcessors skip local packages except MetaProcessor, which only processes local packages. This is because local packages are already in the correct format but need metadata cleanup, while remote packages need asset renaming and material upgrades.

See Also

• PreProcessors — pre-import path translation and visibility

• Processor — abstract base class

• ProcessorTable — lookup table for name mappings