Upgrade guide
Migrate from PicGo
Open the sync section in Settings and choose Migrate from PicGo. PicList imports data.json from PicGo's data directory and, when present, imports picgo.db as piclist.db. These files overwrite the corresponding PicList configuration and gallery, so back up both apps' data directories first.
Restart PicList after the import, check the provider configuration, and verify one upload. Check plugin compatibility separately; importing configuration does not install plugins.
Upgrade Core to 3.0
Install Node.js 22.x, at least 22.13.0, then run:
npm install -g [email protected]
picgo --version
picgo --helpCore 3.0 changes:
| Previous usage or behavior | Current usage |
|---|---|
| ~/.piclist/config.json | data.json takes priority; the old file is a fallback |
| picgo config-list / config-use | Prefer picgo config list / picgo config use |
| Direct construction as the starting example | Initialize with await PicGo.create() |
| CommonJS require('piclist') | Use dynamic import('piclist') |
| Running the command without arguments | Opens the TUI in an interactive terminal; shows help otherwise |
When migrating a script, select the intended file with -c to avoid unexpectedly reading another configuration beside it.
Verify the result
Check that original files remain intact, the destination is correct, URLs work, and output formatting matches your editor. For private storage, also check the lifetime of signed links. Use troubleshooting if a check fails.