Skip to content

LoRA Syntax and Duplicate Filenames

Will Miao edited this page Aug 17, 2026 · 3 revisions

Overview

LoraManager's LoRA nodes (such as Lora Loader (LoraManager), Lora Stacker, and the Text/Prompt (LoraManager) family) take their LoRA list from a text input written in the A1111-style syntax tag <lora:name:1.0>.

The tag format is configurable, and the format you choose affects how LoRAs with identical file names in different subfolders are handled.


The Legacy (A1111) Format

The default format follows the A1111 convention: the tag references the LoRA by file name only, without any folder information.

<lora:name:1.0>

Because only the file name is used, the file name must be unique across all subfolders of your LoRA directory. If two different LoRA files in different folders share the same file name, the tag is ambiguous, and the wrong model may be loaded.


Option 1: Switch to Full Path Syntax

Full path syntax includes the subfolder path in the tag:

<lora:subfolder/name:1.0>

For example, a file at loras/style/anime/x.safetensors is referenced as:

<lora:style/anime/x:1.0>

With full path syntax, identical file names in different folders are no longer ambiguous, and no renaming is needed.

How to switch: open the LoRA Manager settings and set LoRA Syntax Format to Full path (subfolder/name).

After switching, newly copied LoRA syntax includes the subfolder path.


Option 2: Resolve Duplicate Filenames with the Doctor

The Doctor includes a Duplicate Filename Conflicts check that scans your LoRA library for file names that are shared by files in different folders.

How to run it: open the LoRA Manager web UI, click the Doctor button in the toolbar, and look for the Duplicate Filename Conflicts check.

If conflicts are found, click Resolve Conflicts. The extra copies are renamed with a short hash suffix so every file name becomes unique, for example my_lora-a3f7.safetensors (keeps the first copy, renames the rest).

Important: this operation renames files on disk. If you use the legacy syntax format in existing workflows, references to the renamed files may need to be updated. If you later want to remove these hash suffixes, see the Restore Suffixed Filenames script.

When Full path syntax is active, this check reports OK automatically, because duplicate names across folders are no longer ambiguous.


Which Option Should I Choose?

  • Keep your files untouched: switch to Full path syntax. Tags become slightly longer, but every LoRA resolves to the correct file.
  • Keep the simpler A1111-style tags: resolve the conflicts with the Doctor, then update any workflow references that point to the renamed files.

Clone this wiki locally