How to Cancel Figma: Complete Guide

What is Figma

Figma is a cloud-first interface design and prototyping platform used for collaborative product design, wireframing, developer handoff and simple website building. It provides a mix of design canvases, realtime collaboration, an integrated whiteboard (FigJam), and an ecosystem for community resources such as plugins and paid community assets.

Figma offers tiered paid seats that unlock editing, advanced collaboration and administrative controls; pricing and seat definitions are published in USD and have recently been restructured with new seat types (Full, Dev, Collab, View) and pricing updates that took effect for renewals on or after March 11, 2025.

Subscription plans and AU pricing (approx)

Figma lists prices in USD on its site. Localised billing is supported for non-USD currencies; where local AUD pricing is not listed publicly, the table below converts published USD seat prices to AUD as an approximation using recent USD-AUD rates. Use the table for plan-level comparison and treat A$ amounts as approx.

How cancellations typically work for Figma

Figma subscriptions are team- or organisation-based and tied to paid seats. Only account roles with administrative authority (team admin/owner or organisation admin) can execute plan changes that result in downgrades. Paid access usually continues until the end of the current billing period after cancellation; cancellations prevent future renewals but do not automatically generate refunds.

Proration is applied in limited circumstances: adding seats or approved upgrades can trigger prorated charges from the approval date to the billing period end. Removing seats typically does not reduce the already-billed amount for the current period. Annual plans are paid upfront and are treated as paid for that term unless an exception is granted by support.

Plugin subscriptions and one-off purchases from the Figma Community have distinct refund rules; community resources or plugin subscriptions are generally non-refundable after purchase or are subject to a short automatic refund window (for one-off purchases). Plugin subscriptions are commonly noted as non-refundable, with access remaining until billing period end after cancellation.

Customer experience analysis with cancellations

What users report

Public feedback collected from support pages and review aggregators reveals recurring themes: frustration with unexpected automatic renewals, strict application of “no refund” positions on renewals, and cases where billing errors were fixed after support intervention. Several users emphasise the need to monitor renewal dates because Figma does not always send renewal reminders.

Recurring issues and practical takeaways

Users commonly encounter these practical consequences: downgrades that leave files read-only when free-tier limits are exceeded; charges for added seats that are prorated and then appear on the next invoice; and disputes over duplicate or erroneous charges that required support review. There are also reported positive outcomes where support corrected clear billing mistakes or refunded duplicate charges.

Documentation checklist

• Account identifiers: record the team or organisation name and the admin/owner account that controlled the subscription.
• Invoice history: keep copies of the original invoice, renewal invoice, and any produced receipts.
• Billing cycle dates: note the subscription start date, billing period, and next renewal date as shown on invoices.
• Seat changes log: capture dates when seats were added or removed and any prorated charges.
• Plugin/resource receipts: preserve purchase confirmations for community resources and plugins; these often have separate refund rules.
• Support interactions: record dates, ticket references and a concise summary of support responses where disputes occurred.

Common pitfalls and mistakes to avoid

• 1. Assuming immediate loss of files: cancelling does not delete files; it may restrict editing if free plan limits are exceeded.
• 2. Expecting automatic refunds for renewals: Figma’s default position is that payments are non-refundable for renewals; refunds are discretionary.
• 3. Overlooking seat additions: adding seats mid-cycle can trigger prorated charges that affect the next invoice.
• 4. Failing to retain evidence: absence of invoices or records weakens dispute claims under consumer law.
• 5. Confusing community sales with subscriptions: one-off community purchases and plugin subscriptions have separate refund windows and policies.

Disputes, refunds and consumer rights

Under consumer protection law, digital services must be supplied with acceptable quality and fit for purpose. If Figma fails to deliver core features or there is a significant platform defect, consumer guarantees may give rise to a refund or other remedy even if the provider’s published policy says no refund.

Practical implications: billing errors, duplicate charges or supply failures are prima facie grounds to seek remediation. Where a business refuses a reasonable remedy for a major failure, regulatory bodies such as the national consumer regulator may be able to assist. Keep factual records and timelines to support any claim.

What to expect after cancelling a Figma subscription

After a cancellation is processed the paid plan typically remains active until the end of the current billing period. Access changes (for example, reduced editing rights) take effect when the billing period lapses and free-tier limits apply. Files are not deleted by an ordinary cancellation but may be locked for editing if seat or file limits are exceeded.

If a charge posts after the renewal date, cancelling will usually stop future charges; the renewed period is commonly treated as paid. Successful refunds for post-renewal charges are discretionary and often require evidence of error or a major service failure.

Plugin subscriptions specific considerations

Plugin subscriptions sold through the Figma Community are governed by the Community and payments terms. Public guidance indicates plugin subscriptions are generally non-refundable and that cancellation preserves access until the end of the billing cycle. Record plugin receipts and the purchase date carefully if you anticipate disputing a charge.

Plan features comparison

Legal documentation and record retention recommendations

From a contractual and dispute-avoidance perspective, maintain the following for at least 24 months after cancellation: invoices, seat-change records, screenshots of plan settings and any correspondence about charges. These items strengthen claims under consumer law or payment disputes.

• Invoices: save PDFs of all bills and receipts.
• Plan screenshots: capture plan and seat counts as shown in admin/billing pages.
• Charge ledger: create a concise ledger with dates, amounts and invoice numbers.

How to approach a billing dispute

When a billing discrepancy arises, follow a structured evidence-first approach: compile invoices and payment proofs, identify the exact charge date and amount, and prepare a succinct timeline describing the issue and why it is a billing error or major service failure.

If the provider declines remedial action, consumer protection bodies can assess whether the conduct breaches consumer guarantees or fair trading laws. Regulatory intervention is fact-specific; keep documentation organised and factual.

Address

• Address: UNIT 3602, 184 Forbes Street, Darlinghurst, NSW 2010, Australia

What to do after cancelling Figma

After cancellation, immediately reconcile active projects against free-tier limits and reassign or export editable copies where continued editing is required. Plan seat allocation for collaborators to avoid work interruptions when the downgrade takes effect.

Keep a final audit of invoices and seat counts for the period immediately after cancellation. If a post-cancellation charge appears, compare the charge to your invoice timeline and escalate with supporting documentation to the payment provider or regulator if a billing error is not resolved amicably.