Guide / RIGCHECK
What to check before re-importing a PSD into Live2D Cubism
Before replacing a PSD, identify what must remain stable between the file that was first imported and the updated file. RigCheck v0.1 does not compare two PSDs, but it can review the current PSD before re-import.
Your PSD is analyzed in your browser and is not uploaded to our server.
Run the local PSD checkReview these items before replacement
- Keep the previously imported PSD instead of overwriting it.
- Manually review layer and group names, hierarchy, order, additions, and deletions.
- Avoid introducing duplicate layer or group names.
- Save the updated file in an importable PSD state.
- Confirm which PSD is selected in Cubism's re-import settings.
Keep a reference PSD
Keep the PSD that was first imported into the model and the updated PSD as separate files. Version or purpose labels in filenames make it easier to track which source image the current model uses.
Review the structural changes manually
Live2D's official material warns that changing or duplicating part names, layer names, group names, or layer order can lead to problems. A matching name by itself does not prove that the same ArtMesh mapping will be preserved.
- Review renames, duplicate names, parent moves, deletions, and additions.
- If the layer order changed, confirm the display order and part mapping in Cubism.
- After a large shape change, check whether the artwork extends beyond the mesh.
Review the Cubism replacement flow
After confirming that the PSD is ready for import, open the model and load the PSD. In the model settings, choose the add or replace flow, select the target PSD in re-import settings, and verify the result on the model.
Where RigCheck helps
A local preflight can catch RGB/8-bit issues, profile warnings, duplicate names, masks, and other structural details before the replacement step. It is not a two-file comparison and does not guarantee the ArtMesh result, so keep the manual review and Cubism check.
Official sources
Use the Live2D documentation for detailed conditions and version-specific behavior. These links are the sources summarized in this guide.