Deploy to Cloudflare Pages

Before you start

• A Cloudflare account

• An API token with Cloudflare Pages → Edit permission (Swebsy’s link adds Account Settings → Read, so it can fill in your Account ID)

Single files must stay under 25 MiB

Cloudflare Pages allows a maximum of 25 MiB for each individual site asset, and at most 20,000 files per deployment. Swebsy checks both before uploading anything and names the offending file, so an oversized asset fails fast rather than part-way through a deploy. Compress large images and videos beforehand, or host them separately, such as in Cloudflare R2.

Where your API token lives

The token is encrypted and saved on this device only, for this site. It stays after a reload, so you enter it once. It is never written to your project, your cloud copy, or an export, and it is erased when you sign out. On another device or browser you enter it again. Cloudflare’s API cannot be called directly from a browser, so Swebsy relays the call — the relay forwards your token to a fixed list of Cloudflare Pages endpoints and nothing else.

Create an API token

Swebsy needs a key that lets it upload to Cloudflare Pages and read your account ID — nothing else.

1. In Swebsy, click How to get a token, then the Cloudflare API tokens link. It opens Cloudflare’s token form already filled in with two permissions: Cloudflare Pages set to Edit, and Account Settings set to Read (so Swebsy can fill in your Account ID).

2. Click Continue to summary, then Create Token.
3. Copy the token. Cloudflare shows it only once.

One-time setup in Swebsy

1. Click Publish at the right of the topbar and choose Cloudflare Pages — until it is set up, that opens its setup in Settings → Deployment.

2. Paste your API token. Swebsy fills in your Account ID from it — if the token reaches several accounts, pick one from the list. If it stays empty, paste the 32-character code from your Cloudflare dashboard’s address, dash.cloudflare.com/<Account ID>/…. Swebsy checks the connection as soon as both are in.

3. Pick a Pages project from the list, or type a new name and choose Create in the list (or click Create project under the field). Swebsy shows the address Cloudflare gives it, such as https://my-site.pages.dev — Cloudflare adds a short suffix when the name is taken elsewhere. If the project already has a live site, Swebsy says that publishing replaces it.

4. Optionally enter a custom domain.

5. Click Deploy now to publish straight away, or Save. If the connection check failed, Save still saves, and says publishing won’t work until it’s fixed.

Cloudflare Pages configuration lives in Settings → Deployment.

Deploy

1. Click Publish at the right of the topbar.

2. If Cloudflare Pages is the site’s host, click Publish on its card at the top of the menu: it publishes straight away. Otherwise click Cloudflare Pages in the list below it.

3. From the list, or when there is a warning, the Deploy review modal opens, showing the target project, live URL, pages, upload size, and any warnings.

4. Click Publish now.

Use Deploy to Cloudflare Pages after Cloudflare Pages is configured.

Review the generated deployment plan before clicking Publish now.

Expected result

Your site is live at the project’s address shown in the review, such as https://<project-name>.pages.dev (or your custom domain). Swebsy always shows and copies this address, which updates on every publish — not the one-off deployment link Cloudflare also creates.

Custom domain

If you entered a custom domain, Swebsy adds it to the Pages project when you publish. Then add a CNAME record for the domain pointing to the project’s address (Swebsy shows it under the field, such as my-site.pages.dev), wherever the domain’s DNS is managed — Cloudflare DNS or your registrar.

Common issues

Token rejected — your token may have expired, been revoked, or lack the Cloudflare Pages → Edit permission. The Publish menu then shows Token rejected with a Fix in settings button, which opens the token’s Replace. Create a new token from How to get a token and paste it there.

Project not found — open Settings → Deployment (the failed publish has an Open Cloudflare Pages settings button), then pick a project or click Create project.

Large site times out — very large sites (>50 pages, many images) may hit Cloudflare’s Direct Upload limits. Try reducing image sizes before deploying.

Single file upload fails — Cloudflare Pages rejects individual site assets larger than 25 MiB. Compress the file or host it outside the Pages deploy.