Direct HTTPS links

Use explicit, versioned file addresses to retrieve published content.

A URL identifies one version

Direct file addresses follow this structure:

/files/RESOURCE_ID/v000001/filename.ext

RESOURCE_ID is generated by the service; the version number increases for each upload to that resource. The filename is a safe label generated when the version is created. Editing the display name later does not change this address.

Verify a download

Copy a published URL from the library, download the file and compare its SHA-256 with the resource details page.

curl --fail --location --output download.txt "COPIED_PUBLIC_URL"
sha256sum download.txt

Replace COPIED_PUBLIC_URL with a real published address. On Windows, use Get-FileHash .\download.txt -Algorithm SHA256 in PowerShell.

Public means public

Anyone with a published URL can download the file. No private access control or expiring links are provided. Withdrawal prevents new origin downloads, but it cannot recall a copy someone already downloaded.

Explicit page addresses

Use links such as /library/index.html and /library/resource.html?id=RESOURCE_ID. Some delivery providers treat directory URLs differently from explicit filenames. A working file URL does not guarantee that the domain root is handled the same way.

Verify delivered bytes

Open a resource and select Verify download to compare the actual response with the published SHA-256, byte size and MIME. The Status page offers the same check for a selected published version. Checks download the file and report actual HTTP results and elapsed time. A successful check applies to that version at that time.

Website and file delivery

Browse resources and version history on the main website. Use Copy URL for the current file delivery address, rather than changing its hostname by hand. The library uses this address consistently for previews, downloads and integrity checks. These file URLs are independent of the page used to discover them.