> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/account-and-team/billing-and-plans/how-to-cancel-subscription.md).

# How to cancel subscription

Cancel your paid subscription, return to the free plan at the end of the billing cycle, and see what access you keep.

Cancel a paid plan at any time from Account settings. Your account stays active on its current plan until the end of the billing cycle, then moves to the free plan. You are not billed again.

{% hint style="warning" icon="list-check" %}

#### Prerequisites

You need Admin permissions at the account level. Cancellation is done in Account settings.
{% endhint %}

#### Cancel your subscription

{% stepper %}
{% step %}
**Open Account settings**

Click your account name at the top of the left sidebar, then open **Account settings**.
{% endstep %}

{% step %}
**Click Cancel subscription**

Find your current plan and click **Cancel subscription**.
{% endstep %}

{% step %}
**Confirm the cancellation**

Type **CANCEL** to confirm, then submit. Your plan stays active until the end of the current billing cycle.
{% endstep %}
{% endstepper %}

#### What happens after you cancel

* Your account returns to the **free** plan at the end of the billing cycle, and you are not charged again.
* Free-plan limits apply again (for example, up to 10 journey maps and personas, and a single personal workspace). Content over those limits stays, but paid features switch off and you can't create new content beyond the limits. Upgrade again and everything is back as it was.
* Cancelling does not delete your data. If you want to remove your account and its data entirely, see [How to delete your account](/account-and-team/billing-and-plans/how-to-delete-your-account.md) instead.

{% hint style="success" %}
Changed your mind? You can [upgrade again](/account-and-team/billing-and-plans/how-to-upgrade-or-downgrade.md) at any time, before or after the downgrade takes effect.
{% endhint %}

#### Related topics

<table data-column-title-hidden data-view="cards"><thead><tr><th>Article</th><th>What it covers</th><th data-hidden data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>How to upgrade or downgrade</strong></td><td>Move to a paid plan or change tiers, and adjust your seats.</td><td><a href="/account-and-team/billing-and-plans/how-to-upgrade-or-downgrade.md">Upgrade or downgrade</a></td></tr><tr><td><strong>How to delete your account</strong></td><td>Permanently remove your account and its data, instead of just cancelling.</td><td><a href="/account-and-team/billing-and-plans/how-to-delete-your-account.md">Delete your account</a></td></tr><tr><td><strong>What is included in each plan</strong></td><td>See what the free plan includes once your subscription ends.</td><td><a href="/account-and-team/billing-and-plans/what-is-included-in-each-plan.md">What's included in each plan</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdesk.smaply.app/account-and-team/billing-and-plans/how-to-cancel-subscription.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.