feat: add docs

Author: Molunerfinn

docs/api/index.md

@@ -359,6 +359,56 @@ Same as above, but does not support `config`.
 
 Same as above, but does not support `config`.
 
+## uploaderConfig <Badge text="1.8.0+" />
+
+Uploader multi-config manager.
+
+It manages per-uploader named configs stored under `uploader.<type>` and keeps `picBed.<type>` synced as a mirror of the active config.
+
+Config names are matched case-insensitively (whitespace is trimmed).
+
+### uploaderConfig.listUploaderTypes()
+
+List installed/available uploader types.
+
+### uploaderConfig.getConfigList(type)
+
+Get all configs for an uploader type.
+
+### uploaderConfig.getActiveConfig(type)
+
+Get the active config for an uploader type (may be `undefined` if no configs exist).
+
+### uploaderConfig.use(type, configName?)
+
+Activate a config (by name) for an uploader type, and set it as the current uploader (`picBed.current` / `picBed.uploader`).
+
+### uploaderConfig.createOrUpdate(type, configName?, configPatch?)
+
+Create a config or update an existing config (by name), and **activate it on save**.
+
+### uploaderConfig.copy(type, configName, newConfigName)
+
+Copy a config into a new config name (**does not** switch current uploader).
+
+### uploaderConfig.rename(type, oldName, newName)
+
+Rename a config.
+
+### uploaderConfig.remove(type, configName)
+
+Remove a config. If you remove the last config, PicGo clears `picBed.<type>` to avoid credential residue.
+
+Example:
+
+```js
+// Switch to a named uploader config
+picgo.uploaderConfig.use('github', 'Work')
+
+// Create/update a config and activate it
+picgo.uploaderConfig.createOrUpdate('github', 'Work', { repo: 'user/repo' })
+```
+
 ## Request.request <Badge type="warning" text="deprecate" />
 
 **Since v1.5.0 this property is deprecated. Use [`ctx.request`](#request) instead.**

docs/guide/commands.md

@@ -20,9 +20,10 @@ $ picgo -h
     install|add [options] <plugins...>   install picgo plugin
     uninstall|rm <plugins...>            uninstall picgo plugin
     update [options] <plugins...>        update picgo plugin
-    set|config <module> [name]           configure config of picgo modules
+    set|config <module> [name] [configName]  configure config of picgo modules
     upload|u [input...]                  upload, go go go
-    use [module]                         use modules of picgo
+    use [module] [name] [configName]     use modules of picgo
+    uploader [command]                   manage uploader configurations
     i18n [lang]                          change picgo language
     help [command]                       display help for command
 ```
@@ -46,9 +47,9 @@ The CLI is built with [commander.js](https://github.com/tj/commander.js/) and [i
 ```bash
 $ picgo use -h
 
-  Usage: use [module]
+  Usage: use [module] [name] [configName]
 
-  use modules of picgo
+  use a module (uploader/transformer/plugin) of picgo
 ```
 
 PicGo ships with the following built-ins:
@@ -84,28 +85,60 @@ $ picgo use
 (Move up and down to reveal more choices)
 ```
 
+Starting from PicGo-Core `v1.8.0`, uploaders support multiple named configs. If an uploader has multiple configs, the interactive flow will ask you to choose one. You can also specify it directly:
+
+```bash
+picgo use uploader <type> <configName>
+```
+
+`configName` is matched case-insensitively.
+
 After you choose, PicGo will upload using the selected module. Some modules need configuration before you can use them (for example, tokens/keys for an image host). In that case, use `set|config` (described below) to configure the module.
 
-## config|set
+## uploader <Badge text="1.8.0+" />
+
+Manage uploader configurations (multi-config).
+
+- `picgo uploader` opens an interactive prompt (list/rename/copy/delete).
+- `picgo uploader list [type]` lists configs (marks current uploader and default config).
+- `picgo uploader rename <type> <oldName> <newName>`
+- `picgo uploader copy <type> <configName> <newConfigName>` (does not switch current uploader)
+- `picgo uploader rm <type> <configName>`
+
+Config names are matched case-insensitively.
+
+Examples:
+
+```bash
+picgo uploader list
+picgo uploader list github
+picgo uploader rename github Work Personal
+picgo uploader copy github Work Staging
+picgo uploader rm github Staging
+```
+
+## set
 
 > Configure module settings. There are three kinds of modules: 1) transformer 2) uploader 3) plugins
 
 ```bash
 $ picgo set -h
 
-  Usage: set|config [options] <module> [name]
+  Usage: set [options] <module> [name] [configName]
 
-  configure config of picgo modules
+  configure config of picgo modules (uploader/transformer/plugin)
 
   Options:
 
     -h, --help  output usage information
 ```
 
 ::: tip Tip
-Most of the time you only need to configure an Uploader. You can run `picgo set uploader` (or `picgo set uploader weibo|tcyun|...`) to jump straight into the interactive prompt.
+Most of the time you only need to configure an uploader. You can run `picgo set uploader` (or `picgo set uploader <type> [configName]`) to jump straight into the interactive prompt.
 :::
 
+Starting from PicGo-Core `v1.8.0`, `set uploader` works with uploader multi-config: you can choose an existing config (by name) or create a new one, and the saved config becomes the active config for that uploader.
+
 For the detailed configuration fields of built-in uploaders (image hosts), refer to PicGo’s configuration [wiki](https://github.com/Molunerfinn/PicGo/wiki/%E8%AF%A6%E7%BB%86%E7%AA%97%E5%8F%A3%E7%9A%84%E4%BD%BF%E7%94%A8)。
 
 If an uploader/transformer/plugin has no configurable options, PicGo will still report success—this is expected.

docs/guide/config.md

@@ -190,6 +190,51 @@ Example:
 }
 ```
 
+## uploader <Badge text="1.8.0+" />
+
+PicGo supports multiple named configurations per uploader type.
+
+The source of truth is stored under `uploader.<type>`:
+
+- `uploader.<type>.configList`: an array of configs.
+- `uploader.<type>.defaultId`: the `_id` of the active config.
+
+Each item in `configList` includes metadata fields:
+
+- `_id` (UUID v4)
+- `_configName` (unique within the same uploader type, case-insensitive)
+- `_createdAt` / `_updatedAt` (timestamps)
+
+For plugin compatibility, `picBed.<type>` is a **read-only mirror** of the active config and will be overwritten when you switch configs.
+
+::: tip Migration
+If you previously configured an uploader under `picBed.<type>`, PicGo migrates it automatically on startup.
+:::
+
+Example:
+
+```json
+{
+  "uploader": {
+    "github": {
+      "defaultId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+      "configList": [
+        {
+          "_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+          "_configName": "Work",
+          "_createdAt": 1700000000000,
+          "_updatedAt": 1700000000000,
+          "repo": "user/repo",
+          "token": "******"
+        }
+      ]
+    }
+  }
+}
+```
+
+To manage or switch configs, see [CLI Commands](/guide/commands) (`picgo use uploader ...`, `picgo uploader ...`) or use the Node.js API (`ctx.uploaderConfig`).
+
 ## picgoPlugins
 
 This section stores all plugin names and is mainly used to determine whether a plugin is enabled or disabled. **It is generated by PicGo automatically—you don’t need to edit it.**
@@ -203,6 +248,159 @@ Example:
 }
 ```
 
+## settings
+
+General settings not tied to a specific uploader/transformer/plugin.
+
+### settings.urlRewrite.rules <Badge text="1.8.1+" />
+
+Opt-in URL rewrite rules. When configured, PicGo applies URL rewrite **after uploader execution** and **before `afterUploadPlugins`**.
+
+- type: Array\<Rule\>
+- default: not set (no rewrite; no warnings)
+
+Each rule supports:
+
+- `match` (string, required): JavaScript `RegExp` source (no surrounding `/`).
+- `replace` (string, required): Replacement string (supports `$1`, `$2`, ...).
+- `enable` (boolean, optional): defaults to `true`; only explicit `false` disables the rule.
+- `global` (boolean, optional): maps to the regex `g` flag; defaults to `false`.
+- `ignoreCase` (boolean, optional): maps to the regex `i` flag; defaults to `false`.
+
+Behavior:
+
+- Rules are evaluated in array order; **first enabled match wins** (only one rule is applied per image).
+- If rewrite changes `imgUrl`, PicGo stores the original URL in `originImgUrl` (set once and never overwritten).
+- Invalid regex patterns are logged and skipped without failing the upload.
+- If a rewrite produces an empty string, PicGo logs a warning and continues.
+
+#### For plugin authors and Node.js users
+
+- `afterUploadPlugins` will see the **rewritten** `imgUrl` in `ctx.output`; use `originImgUrl` to access the original URL produced by the uploader.
+- `picgo.upload()` (Node.js API) returns `IImgInfo[]` with the **rewritten** `imgUrl`; use `originImgUrl` if you need the pre-rewrite value.
+- `originImgUrl` is only set when PicGo actually rewrites the URL; otherwise it stays `undefined`.
+
+#### Examples
+
+Example (simple prefix rewrite / switch to CDN):
+
+Rewrite:
+
+- `https://example.com/images/2026/1.png`
+- → `https://cdn.example.com/blog-images/2026/1.png`
+
+```json
+{
+  "settings": {
+    "urlRewrite": {
+      "rules": [
+        {
+          "match": "https://example.com/images/",
+          "replace": "https://cdn.example.com/blog-images/"
+        }
+      ]
+    }
+  }
+}
+```
+
+Example (ignore case: normalize file extension):
+
+Rewrite:
+
+- `https://cdn.example.com/blog-images/2026/1.PNG`
+- → `https://cdn.example.com/blog-images/2026/1.png`
+
+```json
+{
+  "settings": {
+    "urlRewrite": {
+      "rules": [
+        {
+          "match": "PNG",
+          "replace": "png",
+          "ignoreCase": true
+        }
+      ]
+    }
+  }
+}
+```
+
+Example (global: replace all underscores in the URL):
+
+Rewrite:
+
+- `https://cdn.example.com/blog_images/2026/hello_world.png`
+- → `https://cdn.example.com/blog-images/2026/hello-world.png`
+
+```json
+{
+  "settings": {
+    "urlRewrite": {
+      "rules": [
+        {
+          "match": "_",
+          "replace": "-",
+          "global": true
+        }
+      ]
+    }
+  }
+}
+```
+
+::: tip Regex and escaping
+`match` is a JavaScript regular expression source. For advanced patterns you may need to escape backslashes in JSON strings, e.g. `\\.` for a literal dot.
+:::
+
+Advanced: capture groups (`$1`, `$2`, ...)
+
+Rewrite:
+
+- `https://example.com/images/2026/1.png`
+- → `https://cdn.example.com/blog-images/2026/1.png`
+
+If your `match` uses parentheses to capture parts of the URL, you can reference them in `replace` (e.g. `$1` for the first group, `$2` for the second).
+In this example, `$1` is the captured `images`, and `$2` is the rest of the path (`2026/1.png`):
+
+```json
+{
+  "settings": {
+    "urlRewrite": {
+      "rules": [
+        {
+          "match": "^https://example\\.com/(images)/(.*)$",
+          "replace": "https://cdn.example.com/blog-$1/$2"
+        }
+      ]
+    }
+  }
+}
+```
+
+Advanced example (rewrite GitHub raw URLs to jsDelivr):
+
+Rewrite:
+
+- `https://raw.githubusercontent.com/user/repo/main/path/to/1.png`
+- → `https://cdn.jsdelivr.net/gh/user/repo@main/path/to/1.png`
+
+```json
+{
+  "settings": {
+    "urlRewrite": {
+      "rules": [
+        {
+          "match": "^https://raw\\.githubusercontent\\.com/([^/]+)/([^/]+)/([^/]+)/(.*)$",
+          "replace": "https://cdn.jsdelivr.net/gh/$1/$2@$3/$4"
+        }
+      ]
+    }
+  }
+}
+```
+
 ## transformer
 
 This section stores configuration for Transformers provided by third-party plugins.