Webflow Site Plan Cancellation Guide: Downgrade Timing and Refund Rules
Start here: Webflow Site plans can be downgraded to Starter at the end of the current billing period or immediately; Webflow generally does not refund unused time simply because a plan is canceled. This guide explains the current process, timing, exceptions and evidence to retain.
The useful way to read Webflow is from the account outward: first the Site plan billing panel, then the billing-period end, then the hosting downgrade. That sequence keeps the site-plan closeout tied to the customer’s own transaction instead of a generic cancellation example.
Webflow plan-impact map
| Issue | Current rule |
|---|---|
| Refund or credit boundary | Canceling a paid Webflow Site plan means downgrading the site to the free Starter plan. |
| Channel, product or fare exception | An end-of-period downgrade preserves paid Site plan features until the current billing period finishes, while an immediate downgrade removes paid hosting features right away. |
| Scope of the rule | Webflow says it generally does not offer refunds or automatic credits for unused time when a paid plan is canceled early, subject to limited exceptions. |
| Deadline or renewal point | Canceling a Site plan can unpublish custom domains and affect CMS, Ecommerce, custom code and other paid capabilities, so plan preparation matters. |
Webflow: Refund or credit boundary
The refund or credit boundary question for Webflow is resolved by one concrete rule: Canceling a paid Webflow Site plan means downgrading the site to the free Starter plan. Read that rule against the Site plan billing panel, not against a generic example. The billing-period end is the practical boundary, while the hosting downgrade is the end state to verify. If the screen or receipt shows a narrower condition, keep that narrower condition in the site-plan closeout.
For Webflow, pair that point with this second rule: An end-of-period downgrade preserves paid Site plan features until the current billing period finishes, while an immediate downgrade removes paid hosting features right away. Site publishing, CMS behavior, and billing can change at different moments, so the closeout should show which effect belongs to which date.
Webflow: Channel, product or fare exception
The channel, product or fare exception question for Webflow is resolved by one concrete rule: An end-of-period downgrade preserves paid Site plan features until the current billing period finishes, while an immediate downgrade removes paid hosting features right away. Read that rule against the Site plan billing panel, not against a generic example. The billing-period end is the practical boundary, while the hosting downgrade is the end state to verify. If the screen or receipt shows a narrower condition, keep that narrower condition in the site-plan closeout.
For Webflow, pair that point with this second rule: Webflow says it generally does not offer refunds or automatic credits for unused time when a paid plan is canceled early, subject to limited exceptions. Site publishing, CMS behavior, and billing can change at different moments, so the closeout should show which effect belongs to which date.
Webflow: Scope of the rule
The scope of the rule question for Webflow is resolved by one concrete rule: Webflow says it generally does not offer refunds or automatic credits for unused time when a paid plan is canceled early, subject to limited exceptions. Read that rule against the Site plan billing panel, not against a generic example. The billing-period end is the practical boundary, while the hosting downgrade is the end state to verify. If the screen or receipt shows a narrower condition, keep that narrower condition in the site-plan closeout.
For Webflow, pair that point with this second rule: Canceling a Site plan can unpublish custom domains and affect CMS, Ecommerce, custom code and other paid capabilities, so plan preparation matters. Site publishing, CMS behavior, and billing can change at different moments, so the closeout should show which effect belongs to which date.
Webflow: Deadline or renewal point
The deadline or renewal point question for Webflow is resolved by one concrete rule: Canceling a Site plan can unpublish custom domains and affect CMS, Ecommerce, custom code and other paid capabilities, so plan preparation matters. Read that rule against the Site plan billing panel, not against a generic example. The billing-period end is the practical boundary, while the hosting downgrade is the end state to verify. If the screen or receipt shows a narrower condition, keep that narrower condition in the site-plan closeout.
For Webflow, pair that point with this second rule: Canceling a paid Webflow Site plan means downgrading the site to the free Starter plan. Site publishing, CMS behavior, and billing can change at different moments, so the closeout should show which effect belongs to which date.
Shut down a Webflow Site plan cleanly
Step 1: Open Site settings > Plans for the exact site and identify whether add-ons or Ecommerce features must be removed first
This action changes the Webflow file from research to execution. Complete the step on the correct Site plan billing panel, note the time, and retain the provider confirmation. The rule that frames it is: Canceling a paid Webflow Site plan means downgrading the site to the free Starter plan. If the site status does not update as expected, keep the site-plan closeout open instead of treating the hosting downgrade as final.
Step 2: Choose whether the downgrade should wait until the billing period ends or happen immediately
This action changes the Webflow file from research to execution. Complete the step on the correct Site plan billing panel, note the time, and retain the provider confirmation. The rule that frames it is: An end-of-period downgrade preserves paid Site plan features until the current billing period finishes, while an immediate downgrade removes paid hosting features right away. If the site status does not update as expected, keep the site-plan closeout open instead of treating the hosting downgrade as final.
Step 3: Use Downgrade to Starter and read the effective-date warning before confirming
This action changes the Webflow file from research to execution. Complete the step on the correct Site plan billing panel, note the time, and retain the provider confirmation. The rule that frames it is: Webflow says it generally does not offer refunds or automatic credits for unused time when a paid plan is canceled early, subject to limited exceptions. If the site status does not update as expected, keep the site-plan closeout open instead of treating the hosting downgrade as final.
Step 4: Save the plan-change confirmation and current invoice
This action changes the Webflow file from research to execution. Complete the step on the correct Site plan billing panel, note the time, and retain the provider confirmation. The rule that frames it is: Canceling a Site plan can unpublish custom domains and affect CMS, Ecommerce, custom code and other paid capabilities, so plan preparation matters. If the site status does not update as expected, keep the site-plan closeout open instead of treating the hosting downgrade as final.
Step 5: Prepare domain, CMS, Ecommerce and custom-code workflows for the reduced Starter limits
This action changes the Webflow file from research to execution. Complete the step on the correct Site plan billing panel, note the time, and retain the provider confirmation. The rule that frames it is: Canceling a paid Webflow Site plan means downgrading the site to the free Starter plan. If the site status does not update as expected, keep the site-plan closeout open instead of treating the hosting downgrade as final.
Step 6: If a refund exception is being requested, use Webflow support and treat that request separately from the downgrade itself
This action changes the Webflow file from research to execution. Complete the step on the correct Site plan billing panel, note the time, and retain the provider confirmation. The rule that frames it is: An end-of-period downgrade preserves paid Site plan features until the current billing period finishes, while an immediate downgrade removes paid hosting features right away. If the site status does not update as expected, keep the site-plan closeout open instead of treating the hosting downgrade as final.
Webflow closeout situations
Downgrade at period end
A useful Webflow test case starts with the Site plan billing panel. Suppose the customer has already reached the edge of the billing-period end. Apply this rule: Canceling a paid Webflow Site plan means downgrading the site to the free Starter plan. Then use the account action ‘Choose whether the downgrade should wait until the billing period ends or happen immediately’. The site-plan closeout should preserve the confirmation so a later billing or refund question can be traced to the exact request time.
Immediate hosting downgrade
A useful Webflow test case starts with the Site plan billing panel. Suppose the customer has already reached the edge of the billing-period end. Apply this rule: An end-of-period downgrade preserves paid Site plan features until the current billing period finishes, while an immediate downgrade removes paid hosting features right away. Then use the account action ‘Use Downgrade to Starter and read the effective-date warning before confirming’. The site-plan closeout should preserve the confirmation so a later billing or refund question can be traced to the exact request time.
Site with paid CMS or custom-domain dependencies
A useful Webflow test case starts with the Site plan billing panel. Suppose the customer has already reached the edge of the billing-period end. Apply this rule: Webflow says it generally does not offer refunds or automatic credits for unused time when a paid plan is canceled early, subject to limited exceptions. Then use the account action ‘Save the plan-change confirmation and current invoice’. The site-plan closeout should preserve the confirmation so a later billing or refund question can be traced to the exact request time.
Webflow records to retain
- Site plan billing panel
- the date used for the billing-period end
- the provider confirmation after the request
- any support or case reference
- the final record showing the hosting downgrade
Webflow cancellation FAQ
What is the first Webflow rule to check?
Canceling a paid Webflow Site plan means downgrading the site to the free Starter plan.
Which Webflow date controls timing?
An end-of-period downgrade preserves paid Site plan features until the current billing period finishes, while an immediate downgrade removes paid hosting features right away.
What does Webflow say about refunds or credits?
Webflow says it generally does not offer refunds or automatic credits for unused time when a paid plan is canceled early, subject to limited exceptions.
Which Webflow exception can change the normal path?
Canceling a Site plan can unpublish custom domains and affect CMS, Ecommerce, custom code and other paid capabilities, so plan preparation matters.
When is the Webflow case complete?
The case is complete when the Site plan billing panel and provider confirmation both support the hosting downgrade and no related return, shipment, booking, lesson, or account obligation remains open.
Map the live-site consequences before downgrading Webflow
A Webflow Site plan is tied to more than billing. Before cancellation, inspect the site for a custom domain, CMS collections, Ecommerce features, custom code, and other paid capabilities that may behave differently on Starter. An end-of-period downgrade can preserve paid features until the billing term closes, while an immediate downgrade can remove paid hosting capabilities sooner. The safest closeout begins with a list of what the site currently depends on. Save the billing panel, the custom-domain settings, and any feature configuration that would be difficult to reconstruct. This is especially important for a production site where a billing action can affect publishing or collection limits. The goal is to avoid a situation in which the customer successfully stops the plan but unintentionally changes the public site before backups, exports, or migration steps are complete.
Webflow refunds are separate from a plan downgrade
Webflow’s support material distinguishes the mechanics of downgrading from the question of whether money is returned. The ordinary cancellation path should not be described as an automatic refund for unused time. If the customer believes an exception or billing error applies, save the invoice and open the refund question separately. A useful record shows the plan type, billing frequency, invoice date, requested downgrade date, and whether the change was immediate or scheduled for period end. That information lets support see the billing context without mixing it with a site-configuration problem. If a refund is not available, the customer should still verify that the next renewal is stopped and that the site lands on the intended plan. The financial result and the hosting result can be correct even when they are different from each other.
Choose immediate versus end-of-period change deliberately
The timing choice in Webflow matters. A customer who wants to keep the live site unchanged through the end of the paid term may prefer a scheduled downgrade when that option is available. A customer who wants paid hosting removed immediately must be prepared for the site-level consequences at the same time. Before choosing, compare the end date on the billing panel with the operational need for the site. If a domain transfer, CMS export, code backup, or migration is planned, schedule those tasks before the paid capabilities disappear. Save the downgrade confirmation and then verify both the billing status and the published site. A good closeout does not treat the account page as the only source of truth; it also checks what visitors can access and what the editor can still manage after the plan change.
Webflow closeout checklist after the billing change
After the downgrade is submitted, revisit the site plan page and note the effective date. Confirm whether the custom domain is still connected, whether publishing behaves as expected, and whether the project now shows the intended plan. If the site was supposed to stay live until period end, check again near that date rather than assuming the transition will happen perfectly. Keep the invoice and downgrade record until the next renewal date passes without a new charge. If the account contains multiple sites or workspaces, confirm the correct site was changed. This is also the point to verify whether any Workspace plan remains separately billable, because a Site plan cancellation does not necessarily describe every paid relationship in a Webflow account. Treat each paid object as its own closeout item and keep the records distinct.
Final Webflow verification
A Webflow customer should finish the closeout by testing the site as a visitor and as an editor. Confirm whether the custom domain still resolves, whether the project can still be published under the new plan, and whether CMS or Ecommerce content is available at the level expected. If the downgrade was scheduled for the end of the term, note the date and repeat this check after the transition. Also verify that no separate Workspace subscription remains active when the intention was to stop all Webflow billing; Site plans and Workspace plans are different billing objects. If the customer is migrating away, keep DNS, domain, export, and backup records until the new destination is stable. The billing proof should stay with the site-impact notes because those two pieces explain both sides of the change: what Webflow charged and what the site could do afterward. This is a better closeout than treating a cancellation as a purely financial event.
Related RefundGuides resources
- Miro Cancellation & Refund Guide: Paid-Period Access, Unused Time and Outstanding Licenses
- ClickUp Refund Guide: 30-Day First Paid Plan Guarantee, Add-Ons and Auto-Renewal
- Zoom Subscription Cancellation & Refund Guide: Plan Terms, Renewals, Add-Ons and App Stores
Official Webflow sources reviewed
Research date: 2026-09-14. Recheck the live provider source before relying on a deadline, fee, refund window, return condition, or plan rule because provider policies can change.