All sites have different data capacities and resource needs. Data quotas apply to anything making data requests on your site, including the CMS (Content Management System), Datasets, and the Velo Wix Data API.
Your sites' collections and items are hosted by Wix, and there is a limit to the amount of data you can store on your site. This includes primarily your collections and your collection items.
Your site is limited to a maximum number of collections. Once it reaches this limit, you can’t create any more collections. The collection limit doesn't apply to Wix app collections or external database collections connected to your site.
If you downgrade to a lower tier plan, the quota changes to the one defined by the new plan. If your site has more collections than is allowed by the new quota when you downgrade, none of your data is deleted. However, you can't add any new collections to your site until you delete enough existing collections to be below the quota.
Wix limits the total number of collection items your site can have. If your site reaches this limit, you won’t be able to add any more data to any of your collections.
The collection items limit is not applied to Wix app collections or external database collections connected to your site. Collection items can also include media or other files, which have separate limits.
If you downgrade to a lower tier plan, the storage quota changes to the one defined by the new plan. If your site has more than this amount of data when you downgrade, none of your data is deleted. However, you can't add any new data to your site until you delete enough existing data to be below the quota.
The maximum size for a single collection item is 512 KB. If you try to add an item larger than this to a collection, the following error message is displayed in your site log:
WDE0009: Document is too large.
There are also some limits that are specific to certain field types.
Note: If your site exceeds the quota and you delete data to free up space, it may take up to 1 hour before you can add new data to your collections.
Every time you access your data, whether that's to read or to write it, you are making a data request. Wix limits the frequency of your requests and the amount of time a request can take.
Wix limits the number of data requests your site can make per minute. Once a site reaches this quota, subsequent requests during the same minute are not processed and return an error. There are separate quotas for read requests and write requests.
The following API functions count as 1 request towards the read quota:
getItems(For newly requested items that are not currently in your cache.)
The following API functions count as 1 request towards the write quota:
Note: Each use of include in a query counts towards the request quota. For example, the following query counts as 3 read requests:
1wixData.query('Movies')2 .include('director')3 .include('studio')4 .find();
For each request that exceeds the quota, the request fails and the following error is displayed in your site log:
WDE0014: Requests per minute quota exceeded.
When your site makes a data request, the request is sent to a Wix server. Wix places limits on how long the code on the server can run before it times out and returns an error instead of the intended result.
After this, the request times out and the following error message is displayed in your site log:
WDE0028: Operation time limit exceeded.
Each data operation triggered by a request from a site takes up a calculated amount of processing time. For example, one database query may take 5 seconds to process. If a site makes 10 of these requests at the same time, it has used up 50 seconds of processing time.
The amount of processing time your site uses on average depends on the complexity of the requests, the amount of data they process, and the volume of requests. Wix limits the amount of processing time your site can use per minute.
For each request that exceeds the quota, the following error is displayed in your site log:
WDE0122: Processing time quota exceeded.
It's important to understand your database's infrastructure, how it affects data management, and how to use indexes to improve data requests.
Database collections store dynamic content for your site, such as the content that is displayed on sites and site visitor generated content.
Database collections for free and most premium sites are stored in large, multi-tenant databases. This does not mean that your site's data is exposed. It does mean that there are limits on the storage, read/write requests, and indexing resources available to your site. Database collections for sites with the Business Elite plan are stored in dedicated databases, providing them with significantly greater data resources.
A database collection index is a set of keys used to improve performance when searching for data in a database. Indexes can be created on a single collection field or multiple fields. Indexes are added to fields or sets of fields that are used most often when querying the collection to retrieve information.
Collections can have 2 types of indexes:
- Regular: These indexes improve retrieval performance as described above.
- Unique: These are special indexes that improve performance and also enforce the uniqueness of values in the field that they’re defined for.
The Business Elite plan allows you to create any combination of unique or regular indexes up to the amount of indexes in the quota. Other plans include only 1 unique index.
If you downgrade to a lower tier plan, the oldest indexes are maintained up to the new plan's quota. All other indexes on the site are deleted. If you downgrade to a free plan, all indexes are deleted.
Your site may have data usage needs that aren't supported by Wix database collections. In these cases, you can integrate external databases with your site using an external database adaptor.
If you downgrade to a lower tier plan, you can no longer access your external database from your site.