Amplitude limits and quotas

Amplitude enforces limits on monthly event volume, per-project instrumentation counts, string values, chart date ranges, and CSV exports. In-product warnings and email alerts fire before you reach most of them.

Event volume limits

Every organization has a monthly event volume or monthly tracked user (MTU) limit. Your plan or signed agreement sets it, and you can find it in Settings > Organization Settings > Plans & Billing.

Amplitude calculates event volume on a calendar-month basis and resets the count to zero on the first of each month. Any event that Amplitude ingests and processes counts toward the limit.

Customers who exceed the limit might incur overage fees. Amplitude alerts admins by email and in-product when a paid account reaches 80%, 90%, 100%, and 110% of its limit. Free accounts get the first three alerts. For how overage is calculated and billed, refer to the MTU billing guide.

If you're a non-paying customer and you exceed your monthly limit three times, Amplitude blocks your account. While blocked, you can't reach charts and dashboards, but you keep administrative functions such as the User API so you can meet compliance obligations. If you keep exceeding the limit without upgrading, Amplitude deletes the account six months after the initial block.

What counts toward event volume

Events that exceed the per-project event type limit still count toward monthly volume. You can't query them in Amplitude, but Amplitude ingests them and exposes them through the Export API.

Reduce your monthly event volume

Block or delete events you don't need. Amplitude doesn't ingest blocked or deleted events, so they don't count toward your quota. You can unblock or undelete an event at any time, but data sent while an event was blocked isn't retrievable, because Amplitude never ingested it.

For the difference between blocking and deleting, refer to Hide, block, or delete an event or property.

After you block or delete an event, update your instrumentation so it stops sending those events. The cleanest fix is to never send unwanted events in the first place.

To reduce event or user properties, delete the ones you don't need from the property table in Amplitude Data. Changes take about 24 hours to appear.

Instrumentation limits

The default per-project maximums are:

• Event types: 2,000.
• Event properties: 2,000.
• User properties: 1,000.

These are defaults rather than hard ceilings. Contact Amplitude Support to request an increase for your project.

Once you reach a limit, Amplitude stops indexing new values. You can't query data for any event type or property beyond the limit. You can only reach it in raw data through CSV export or the Export API.

For example, an instrumentation bug might send extra event types so that your project exceeds the limit by five. Data for those excess event types appears in Amplitude only after you bring the project back under the limit. Data that Amplitude ingested while you were over the limit stays unqueryable.

There's no limit on the number of values you can send for an event or user property, and no limit on the number of event properties you can attach to a single event.

Property-value dropdowns show a subset of values, ranked by volume rather than by when you first sent them. Amplitude keeps a small number of the highest-volume values seen in real time each day, combined with a much larger set from batch processing. A low-volume value can be missing from a dropdown even though Amplitude ingested it and charts still query it correctly. Derived, lookup, and channel properties have a tighter cap of 1,000 distinct values.

You can delete unneeded event types in Amplitude Data. After you drop below the limit, new event types and properties take about 24 hours to appear.

Character limits for strings

Amplitude limits most property values to 1,024 characters, with two exceptions:

• User property arrays built with append or prepend: the array can grow to 10,000 characters. The initial array still has a 1,024-character limit, so grow it incrementally.
• Properties with property splitting enabled: Amplitude applies a size budget to the combined array contents instead of a per-value character count. The default budget is 100,000 bytes for event properties and 20,000 bytes for user properties. Contact Amplitude Support to adjust either budget for your project.

Amplitude truncates values that exceed these limits.

Limit warnings

Amplitude warns you as you approach event-type, event-property, or user-property limits. View current usage at Settings > Organization settings > Projects, then select a project.

Orange text marks limits you're approaching; red text marks limits you've exceeded. An orange warning bar appears at the top of the page when you're within 10% of a limit, and a red bar appears once you pass one.

Chart limits

These limits apply to Metric Explorer and Event Segmentation charts.

Segmentation module

The date picker limits an inline behavioral cohort to a lookback of about three years. A request for a longer range returns an error.

You can add up to 10 user segments to a chart.

Date picker

Each visualization has its own date range limit:

Charts show a warning when you reach or exceed these limits.

In Metric Explorer, a chart that includes a session metric has a maximum range of one year: 365 days, 52 weeks, 12 months, or 4 quarters.

Breakdown table

The breakdown data table lists the top 100 property values when you apply a group-by. You can select up to 30 segments and show them all on one chart.

Data Tables applies tighter display limits: 100 rows for a single top-level group-by, and 500 rows for multiple group-bys. Metrics that use attribution display far fewer groups. For the full set, refer to Data Tables results and sorting logic.

CSV export limits

Export limits are separate from display limits. A chart can export many more rows than it displays.

Group-by export limits vary by chart:

For example, in Event Segmentation you can export a CSV with 10,000 distinct property values. If your group-by has more than 10,000 possible values, Amplitude exports the top 10,000. The cap is shared across the chart rather than applied per series, so a chart with two events exports up to 5,000 values each. To get the full data table, export to a warehouse instead.

The Data Tables baseline group-by export limit is 10,000, with these exceptions:

• 300 with a conversion metric.
• 100 with a session metric.

When several exceptions apply, the lowest limit wins. For the full set, including how attribution affects a table, refer to Results limits and sorting logic in Data Tables.