PicGo vs PicList

The short version. PicGo defines the plugin format both apps use, ships its own hosting in PicGo Cloud with config and album sync built in, and has 219 plugins on npm written against it. PicList is a fork that bundles watermarking, compression and remote file management into the app itself, and reads PicGo’s plugins rather than having its own.

Use PicGo if you want the larger plugin ecosystem, first access to new extension points, and hosting that works without wiring up WebDAV or Git. Use PicList if you want its built-in image tools and remote file browsing without installing anything, and can live with picking up plugin changes second.

At a glance

Where the features live

This is the difference that matters, and it shows up plainly in what each project’s core package depends on.

PicList-Core ships the storage providers and image tooling directly: the AWS S3 SDK, qiniu, webdav, an SSH client, plus sharp, heic-convert and text-to-svg for watermarking and conversion. Install PicList and all of that is on disk, whether or not you use S3 or ever add a watermark.

PicGo-Core ships neither. PicGo has eight uploaders built into the app — GitHub, Aliyun OSS, Tencent COS, Qiniu, Upyun, SM.MS, Imgur and PicGo Cloud — but the code behind them is not baked into the core, and image processing is absent entirely. Anything else arrives as a plugin.

PicList supports more hosts out of the box. The one that matters is the one it cannot add: PicGo Cloud is a service we run, not an integration with storage you already pay for, so it is the only entry on either list that works before you have an image host at all.

The plugin ecosystem is PicGo’s

PicList is compatible with PicGo plugins — its own README says so, and its plugin loader looks for packages named picgo-plugin-*, exactly the ones PicGo uses.

The asymmetry is in the numbers. npm carries 219 packages published under the picgo-plugin keyword and none under piclist-plugin. When someone writes an uploader for a new image host, they write it for PicGo, and PicList inherits it. That is a real advantage for PicGo users, and also a reason PicList works as well as it does.

It does mean the compatibility runs one way, though. Plugin authors build and test against PicGo, so a plugin tracks new PicGo features as they land; PicList picks them up when it next syncs with upstream. PicList’s own README says it is compatible with most existing PicGo plugins rather than all of them, and where a plugin does not fit, someone has to fork it — picgo-plugin-pic-migrater-piclist exists on npm for exactly that reason.

This also decides who sets the format. The plugin API is PicGo’s, so when PicGo adds a new extension point, plugins can use it immediately and PicList gains it when it next merges upstream. That gap is structural rather than a matter of anyone’s release speed — a downstream fork tracks the upstream API, not the other way round.

There is a second-order effect worth knowing about. Because PicList builds watermarking, compression and format conversion into the app, those can overlap with plugins that do the same job, and you end up deciding which layer owns the transformation. On PicGo there is only one layer: if a plugin is not installed, the step does not happen.

Corrections to comparisons still circulating

PicGo 3.0 landed in July 2026 and several widely-shared comparisons predate it. If you have read that PicGo lacks these, that was true once and is not now:

• Configuration sync. Shipped in v3.0.0 with automatic, server-side and end-to-end encrypted modes.
• Cloud album management and sync. Also v3.0.0, including importing existing local history and syncing across devices through PicGo Cloud.
• Code signing on macOS and Windows. PicGo is signed on both, so the Gatekeeper warnings described in older posts no longer apply.

Where PicList is genuinely ahead

Worth stating plainly rather than leaving for someone else to point out:

• Managing files already on your host. PicList can browse, search, rename and delete remote files across storage providers. PicGo’s album covers what you uploaded through PicGo.
• Image tools with zero setup. Watermark, compress, scale, rotate and convert are built in and configurable per host. PicGo needs a plugin for each.
• A scripting system and themes. Lifecycle scripts without a Node environment, plus a theme repository.

How to choose

Pick PicList if you manage files on your image host from the app itself, or want watermarking and compression without hunting for a plugin first.

Pick PicGo if you want hosting that comes with the app, the widest choice of plugins with no built-in behaviour to work around, or the smallest thing that turns a screenshot into a link.

PicGo Cloud is the part that is not a feature comparison. Every local feature either app ships — watermarking, compression, remote file browsing — is something the other could add. Hosting is not: it needs storage, a CDN, custom domains and someone running them. PicGo Cloud gives you a working image host with a free tier the moment you sign in, and config and album sync ride on the same account. Without a service behind it, syncing means pointing the app at WebDAV or a Git repository you maintain yourself. It is also where new capability lands first, because it is ours to build on rather than a wrapper around storage you supply.

Neither choice locks you in either way. Your images live on the host you configured, not inside the app, and both read the same plugin packages, so switching later costs a reconfiguration rather than a migration — the exception being anything you keep in PicGo Cloud, which travels with the account rather than the app.

Frequently Asked Questions

Q: Is PicList better than PicGo?

A: They optimise for different things. PicList bundles watermarking, compression, cloud file management and themes into the app, so those work the moment you install it. PicGo keeps the core small and moves that kind of feature into plugins, so you install only what you use. If you want cloud storage browsing and image editing with no setup, PicList does more out of the box. If you would rather not carry code for features you never touch, PicGo is the smaller tool.

Q: Is PicList a fork of PicGo?

A: Yes. PicList started from PicGo in January 2023 and describes itself as built upon the foundation of PicGo. It keeps PicGo’s uploader model and its plugin format — PicList loads packages named picgo-plugin-*, the same ones PicGo uses.

Q: Do PicGo plugins work in PicList?

A: Most do, because PicList reads the same picgo-plugin-* packages. The reverse is not really a category: npm carries 219 packages under the picgo-plugin keyword and none under piclist-plugin, so the plugin ecosystem is PicGo’s and PicList consumes it.

Q: Do PicList’s built-in tools conflict with plugins?

A: They can overlap. Watermarking, compression and format conversion exist both as PicList features and as PicGo plugins, so if you install a plugin that does one of those jobs you need to decide which layer performs it. PicGo has no built-in image processing at all, so a plugin is either installed or the step does not happen. PicList also describes itself as compatible with most PicGo plugins rather than all of them, and a few have PicList-specific forks published separately.

Q: Does PicGo have config sync and a cloud album?

A: Yes, since v3.0.0 in July 2026. Configuration sync supports automatic, server-side and end-to-end encrypted modes, and cloud album management syncs across devices through PicGo Cloud. Comparisons written before mid-2026 predate both and are out of date on this point.

Q: Is PicGo signed on macOS and Windows?

A: Yes, on both platforms. Older write-ups describing unsigned builds and Gatekeeper warnings no longer reflect current releases.

Q: Can I switch between them?

A: Both read the same image host configuration and the same plugin packages, so moving across is a reconfiguration rather than a migration. Your uploaded images are unaffected either way — they live on whichever host you configured, not inside the app.

Checked against each project’s public repository and npm in September 2026. PicList is open source at Kuingsmile/PicList; if anything here is out of date, let us know and we will correct it.