Open Usage for the active team
Choose Usage in the Manage sidebar and confirm the team selector in the header. The Tiers tab shows the current tier and plan choices. The Breakdown tab shows current capacity and consumption for the selected team.
The snapshot includes workspaces, users, active projects, task units, and storage. Operational limits can also cover workers, processing availability, saved exports per project, project versions, collection access, single-file upload size, AI Assistant questions per team per day, support level, and retention.
How hourly task units work
Task units are reusable processing slots measured over a rolling hour. Starting a task uses capacity; that capacity returns one hour after it was used, even if the task finished sooner. The Usage charts show the used amount and the time-based return so you can decide whether to wait or change capacity.
Task units are different from worker concurrency. A worker may have a free execution slot while the team has no hourly task units, or the team may have units while every compatible worker is busy or offline. Check both Usage and Workers when queued work does not start.
Compare tiers
Open Pricing from the public site or use the tier cards on Usage. Compare Basic, Plus, Pro, and Ultra by the limits that affect your workflow: team workspaces and members, active projects, workers, hourly task units, continuous processing, project versions, saved exports, custom/private collections, storage, maximum upload, AI Assistant questions, support, and retention. The AI Assistant row shows N/A on Basic, 5 questions / day on Plus, 10 on Pro, and 20 on Ultra. Each daily allowance is shared by the team.
Use the current values displayed on the pricing page rather than relying on an old screenshot or guide. Limits and included capacity can change as the service evolves.
Upgrade through checkout
Choose the desired tier and select its upgrade action. Review the billing period, price, and team receiving the subscription before continuing to checkout. Return to Usage after payment and confirm that Current tier and the capacity snapshot changed.
If an upgrade is complete but the old limits remain visible, refresh Usage and confirm that the same team is active. Contact support with the team name and payment reference if it still does not update.
Assign Patreon benefits
First open account Settings and link Patreon under Linked accounts. Then open Usage for the team that should receive the benefits and use the Patreon subscription assignment control. Only an eligible team owner can make that assignment.
Benefits can be assigned to one team at a time. Moving them to another team can have a cooldown; the interface shows the remaining wait when a switch is unavailable. Before moving benefits, check whether the current team would lose capacity needed by active projects, storage, workers, or exports.
Cancel or request a refund
Manage renewal and submit any refund request through Patreon. Canceling prevents a future renewal according to Patreon's billing rules; it does not automatically reverse a completed payment. Patreon currently accepts refund requests from Billing History within 60 days of the original payment and can direct requests outside that flow to Patreon Product Support.
Read the [Refund Policy](/refund-policy) before submitting a request. Explain which specifically paid limit or benefit was not applied, when the issue occurred, which team or project was affected, and what troubleshooting was attempted. A failed import, task, Editor action, or export is not automatically a subscription failure when the paid capacity itself remained available.
When a team is over a limit
MapToPlay can pause creation or processing when a tier no longer covers the current usage. Open Breakdown to identify the exact limit. Archive or remove work only when it is safe, wait for rolling task units, reassign valid benefits, or upgrade to capacity that covers the team.
Do not delete a project or asset as the first response to a temporary hourly limit. Task units return automatically; deletion is appropriate only for storage or item-count limits when the data is genuinely no longer needed.