Define the fetch prefix separately from the request identifier
Claid's Web Folder setup asks for URL address and storage name. They perform different jobs. URL address supplies the base web address used to locate an image; storage name identifies that configured source in an image-processing request.
The practical configuration unit therefore consists of three values: a URL prefix, a storage name and a representative image path. Write the expected assembled fetch address before saving the configuration. This is a mapping record, not an API response.
For a simple directory convention, choose a prefix ending with / and relative image paths without a leading /. This makes the intended concatenation explicit in the team's own records. Claid's supplied documentation does not establish automatic slash normalization or path repair.
Avoid substituting a storage label for the actual hosting address. A name such as catalog-public is a connector identifier; it is not proof that Claid can retrieve https://media.example.invalid/catalog/sku/front.png.
Prefer a resolved destination, then add Web Folder
Claid advises using a fully resolved URL prefix that does not redirect, explaining that this can speed up fetching on Claid's side. This is a documented recommendation, not a published rule that every redirect causes connection rejection.
The dashboard procedure is to open Storages, choose Connect your storage, select Web Folder, enter URL address and storage name, then choose Add storage.
Save the exact configured prefix and its representative path together. If the resulting image-processing request refers to a different path than expected, first reconcile the stored mapping with the submitted image reference.
Adding the storage and retrieving an image are separate states. The documentation says the storage becomes ready to accept requests; it does not certify a particular source file, host response or image-processing result.
Diagnose configuration errors without confusing them with hosting failures
If an eventual request cannot retrieve its image, check the submitted storage identifier and relative image path against the recorded mapping. A wrong storage name points to connector selection; a wrong path points to address construction.
If the assembled URL is correct but the file is inaccessible, investigate the hosting or delivery environment with an authorized request. The Web Folder page does not provide a guarantee about access control, CDN behavior, supported redirect chains or server responses.
Do not respond to a retrieval problem by regenerating the product artwork. Keep the source asset unchanged until the transport and mapping layer has been separated from the image's content.
Illustrative mapping: one ceramic mug asset
A seller plans a Web Folder named catalog-public. The proposed URL address is https://media.example.invalid/catalog/ and the relative image path is sku/MUG-7/front.png. Concatenating those two address components produces https://media.example.invalid/catalog/sku/MUG-7/front.png.
An alternative short prefix, https://go.example.invalid/catalog/, is hypothetically assumed to redirect to the media host. The seller chooses the direct media prefix instead, following Claid's recommendation. Both domains are deliberately invalid examples; no hosting behavior is claimed.
The seller records catalog-public as the storage name, the complete direct prefix, the relative path and the expected assembled URL. They then configure Web Folder. Before treating the file as usable, they must separately verify the real hosted address and an actual request's result.
| Configuration item | Illustrative value | Role |
|---|---|---|
| URL address | https://media.example.invalid/catalog/ | Prefix used for constructing the requested image address |
| Storage name | catalog-public | Identifier used to select the configured storage |
| Image path | sku/MUG-7/front.png | Relative path appended to the URL prefix |
| Expected assembled URL | https://media.example.invalid/catalog/sku/MUG-7/front.png | Planning result; not a verified fetched resource |
Source and evidence scope
Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.
Official source snapshot checked .
The Claid Web Folder documentation defines the two setup fields, recommends a fully resolved non-redirecting URL prefix and describes the dashboard connection procedure. It does not specify automatic URL normalization, prove file accessibility or guarantee successful image retrieval after storage is added.