Two ways to use V1 models
V1 models (based on journey-ad / Cubism 2~3) are always free. Common ones include 22 / 33, Pio / Tia, Shizuku, Kantai Murakumo, Hyperdimension Neptunia, etc. The first two options under WordPress admin → Live2D settings → "Workshop API type" both run V1.
Form ①: Local
| Item | Description |
|---|---|
| Data source | The V1 models bundled inside the plugin's assets/v1/ directory |
| How it's served | Local REST path /wp-json/live2d/v1/model/* |
| Network required | No — fully served from your own site |
| Best for | The default — install the plugin and it just works |
| Limitation | Models are limited to those bundled with the plugin; for more, use the remote workshop |
How to enable: pick Local for "Workshop API type" and save. The mascot appears immediately.
Form ②: Remote workshop
| Item | Description |
|---|---|
| Data source | Pulls a model catalog from www.live2dweb.com |
| Workflow | After fetching the catalog, downloads to local storage and then uses the V1 pipeline |
| Download location | wp-content/plugins/live-2d/model/ |
| Network required | First-time access to www.live2dweb.com to pull the catalog and download files; afterwards works offline |
| Best for | Users who want more V1 skins than the bundled ones (extra texture variants of 22 / 33, more Pio outfits, …) |
How to enable: pick Remote workshop for "Workshop API type" and save. On the front-end mascot toolbar click "Switch model" to browse the full remote model library.
Which form should I pick?
- First time using the plugin / default experience → pick Local.
- Want more V1 model variants → pick Remote workshop, then click "Switch model" on the front-end to browse the full inventory.
Tip: neither mode requires payment or login. If you want Cubism 4+ MOC3 models (V2), see V2 custom model.
How V1 relates to the browser extension
The browser extension has its own dedicated V1 model library tab whose flow is similar to the WordPress plugin's "Remote workshop": list → download to local (IndexedDB) → use. However the two download libraries are maintained separately: the extension's V1 list is its own bundled catalog (PNG thumbnails + *.textures.json) and never queries www.live2dweb.com. See Chrome / Edge extension.
Common misconceptions
- "Is V1 deprecated?" — No. The V1 pipeline became fully self-hosted in 2.1.3 (no longer depends on third-party sources like fghrsh.net) and is more stable than before. It just won't get new features (blend shapes, super-sampling, things only Cubism 4+ has).
- "Can I run my own V1 model server?" — Yes, see fghrsh/live2d_api (external). But since 2.1.3 the plugin already bundles the common V1 models and a third-party API is usually unnecessary.