Sparkle hosting · Cloudflare R2

Hosting your Sparkle appcast on Cloudflare R2 for free

Your updater needs two things on the web: an appcast XML feed and the signed archives it points to. R2 can serve both without bandwidth charges, and a small app can fit within its monthly free allowances. Here is how to make that setup reliable—not just publicly reachable.

By Francisco Cantu ·

What “free” actually covers

As checked for this November 2026 guide, R2 includes 10 GB-month of Standard storage, 1 million Class A operations, and 10 million Class B operations each month. Internet egress is free. The free allowance does not apply to Infrequent Access storage.

Storage above the Standard allowance costs $0.015 per GB-month; excess Class A operations cost $4.50 per million and Class B operations $0.36 per million. Uploads and listings contribute to Class A usage; reads contribute to Class B usage. Check Cloudflare’s current pricing and billing units before enabling R2.

“Free” is conditional, not an unlimited plan. Old archives use storage, and frequent update checks generate reads. Monitor billing and usage; do not assume a usage notification is a hard spending cap. A domain you buy separately can also cost money.

1. Prepare your release and bucket

Start with a working Sparkle integration and a signed, notarized app. If you have not added the updater yet, follow the Sparkle setup guide. R2 hosts files; it does not sign your app, issue Apple notarization tickets, or generate your Sparkle key.

In the Cloudflare dashboard, enable R2, review its billing requirements, and create a Standard-storage bucket such as my-app-updates. A new bucket is private by default. Keep release artifacts in a dedicated bucket: making it public is not a safe way to share a bucket containing private documents.

Use a predictable object layout:

Example public release objects

myapp/appcast.xml
myapp/MyApp-1.2.0.zip
myapp/MyApp-1.3.0.zip

Use unique archive filenames for each release. Keep older archives that are still referenced by your feed or needed by supported clients.

2. Connect a production download domain

In your bucket’s settings, open Custom Domains and connect a hostname such as updates.example.com from a domain on your Cloudflare account. Follow the R2 dashboard’s domain connection process and wait for the domain to become active; adding a DNS record alone is not the full setup.

The domain makes objects publicly readable. It does not grant visitors permission to write to your bucket. A bucket has no public directory listing, but that is not a privacy boundary: anyone with an object’s URL can fetch it.

Cloudflare’s r2.dev public address is for development, not production. It has variable request and bandwidth limits and lacks the custom-domain caching features. For a shipped updater, use the custom domain. Do not put a login, Cloudflare Access challenge, or browser challenge in front of the appcast or downloads.

3. Upload archives first, then the appcast

For an initial test, the dashboard upload tool is enough. For repeatable uploads, configure an S3-compatible client with R2 credentials scoped to this bucket and only the permissions it needs. Keep credentials private; never put them in your app, feed, repository, or website.

The following AWS CLI example assumes you have installed the CLI and configured a local r2 profile with your R2 credentials. Replace ACCOUNT_ID, bucket name, paths, and version. The account ID is not the API secret.

Upload a release to R2

aws s3 cp "MyApp-1.3.0.zip" \
  "s3://my-app-updates/myapp/MyApp-1.3.0.zip" \
  --profile r2 \
  --endpoint-url "https://ACCOUNT_ID.r2.cloudflarestorage.com" \
  --content-type "application/zip"

aws s3 cp "appcast.xml" \
  "s3://my-app-updates/myapp/appcast.xml" \
  --profile r2 \
  --endpoint-url "https://ACCOUNT_ID.r2.cloudflarestorage.com" \
  --content-type "application/xml" \
  --cache-control "no-cache"

Upload and verify the archive before replacing the feed. Otherwise, Sparkle may discover an update whose download does not exist yet. Upload the exact archive you signed: recompressing or modifying it afterward invalidates the Sparkle signature.

4. Set Sparkle’s public URLs

Set SUFeedURL in your app’s Info.plist to the public HTTPS feed URL—not the private S3 endpoint.

Info.plist feed URL

<key>SUFeedURL</key>
<string>https://updates.example.com/myapp/appcast.xml</string>

Every appcast enclosure must also point to the public archive URL, for example https://updates.example.com/myapp/MyApp-1.3.0.zip. Generate a signed appcast with Sparkle’s publishing tools or HarborPilot, then inspect the XML before uploading it. Do not manually copy another archive’s signature or length.

Changing a feed URL only in a new build will not redirect an already shipped older app. If you are migrating hosts, keep the old URL working or arrange and test an appropriate redirect.

5. Keep the feed fresh without wasting archive caching

Treat the feed and archives differently. appcast.xml changes at the same URL, so use a short cache policy or bypass edge caching for that exact path. Versioned archives can use longer caching because their content should not change.

Do not assume XML is cached by default, and do not assume Cache-Control: no-cache defeats every Cloudflare cache rule. Review the rules on your custom domain. A rule that overrides origin headers can still serve a stale feed. Purge the feed URL after publishing if needed, then inspect the public response.

Check the public feed and archive

curl -fI "https://updates.example.com/myapp/appcast.xml"
curl -fL "https://updates.example.com/myapp/appcast.xml" -o /tmp/appcast.xml
curl -fI "https://updates.example.com/myapp/MyApp-1.3.0.zip"

Look for successful responses, the expected XML rather than an HTML challenge, and the new version in the downloaded feed. Inspect Age, Cache-Control, and CF-Cache-Status when present. These checks prove reachability, not that Sparkle can install the update.

6. Test a real upgrade before announcing it

  • On a Mac without R2 credentials, open the public feed and download URL.
  • Run an older signed app build and choose Check for Updates.
  • Confirm the newer build is found, downloaded, verified, and installed.
  • Keep the private Sparkle signing key backed up securely; it never belongs in the bucket.
  • Review R2 storage and operation usage as your audience grows.

If Sparkle says there is no update, check the build number, feed contents, supported macOS version, and caching. A 403 often means public access or an access rule needs attention; a 404 often means the enclosure URL and object key disagree.

Simplify your next release with HarborPilot.

Once hosting is working, the repetitive part is preparing each release. HarborPilot builds your app, signs it with Developer ID, notarizes and staples it, signs the Sparkle update, and writes the appcast. It can also upload them to your R2 bucket and check they're live, or leave the upload to you.

Sources and further reading

Service limits and Apple requirements can change. Check the linked documentation before publishing. HarborPilot is not affiliated with Apple, Cloudflare, or the Sparkle project.