Image Hosting settings
Use Settings → Image Hosting to define global image-upload candidates. Image host priority 1 has highest priority; blank and duplicate entries are ignored. Tracker policy can restrict the candidates, and a tracker-specific Preferred image host for this tracker setting can override the global preference.
Configure host priority
Choose up to six hosts in preferred order. The Web UI reveals credential fields only for selected hosts.
| Host | Required setting |
|---|---|
| ImgBB | API key |
| ImgBox | None |
| Pixhost | None |
| Lensdump | API key |
| PTScreens | API key |
| OnlyImage | API key |
| Dalexni | API key |
| Zipline | Upload endpoint URL and API key |
| PassTheImage | API key |
seedpool_cdn | API key |
| ShareX | Endpoint URL and API key |
| UTPPM | API key |
Tracker-specific host choices still apply after warning acknowledgement and when existing images are reused. Cached images on another host do not replace the configured choice.
For composite uploads, CLI --imghost (-ih) and API imageHosting.preferredHost also guide automatic screenshot and DVD-menu hosting. Tracker-specific configured hosts take precedence. The preference uses normal host compatibility and fallback rules; compatible saved links can still be reused rather than uploaded again. It is not the same as selecting one explicit host in the Upload Images stage.
When an allowed host fails, upbrr can try the next eligible configured host. A host rejected by the target tracker's policy is skipped regardless of its global position.
Imported tracker images still follow the destination's host policy. upbrr resolves supported thumbnail and proxy URLs to full-size sources where possible. Links tied to the source tracker require an eligible image host; this also applies to images inside imported comparison blocks. If a required image cannot be downloaded or rehosted, preparation reports the failure instead of treating the source URL as a valid destination upload.
For size-limited batch uploads, upbrr respects both the host’s file-count and encoded-size limits, including multipart overhead, by splitting images into separate requests. If one image cannot fit by itself, reduce its file size before retrying. The same limits apply to CLI and Web UI uploads.
Additional hosts
The Additional hosts section contains conditional, tracker-owned integrations. Enable one and enter its API key only when the corresponding tracker advertises support. They are not general global fallback slots.
Verify the change
Save, open Upload Images, select test images, and inspect the planned host per tracker before uploading. A successful image upload does not prove every tracker accepts that host; verify the generated description or dry-run preview too.