# Known limitations

Currently, MeiliSearch has a number of known limitations. Some of these limitations are the result of intentional design trade-offs, while others can be attributed to LMDB, the key-value store that MeiliSearch uses under the hood.

# Design limitations

# Number of query words

Limitation: The maximum number of terms taken into account for each search query is 10. If a search query includes more than 10 words, all words after the 10th will be ignored.

Explanation: Queries with many search terms can lead to long response times. This goes against our goal of providing a fast search-as-you-type experience.

# Database size

Limitation: The default maximum database size is 100GiB. This size can be modified using the options --max-mdb-size & --max-udb-size as described in the configuration reference.

Explanation: MeiliSearch uses two databases: one for storage and one for updates. On launch, LMDB needs to know the maximum size that it will need to reserve on disk for both of them.

# Number of indexes

Limitation: You can create up to 200 indexes in MeiliSearch.

Explanation: This limit has been hard-coded for performance reasons.

# Maximum words per attribute

Limitation: MeiliSearch can index a maximum of 1000 words per attribute. If an attribute contains more than 1000 words, only the first 1000 words will be indexed and the rest will be silently ignored.

Explanation: This limit is enforced for relevancy reasons. The more words there are in a given attribute, the less relevant the search queries will be.

# Other limitations

# Payload size

Limitation: The default limit for the payload size is ~100MB.

Explanation: MeiliSearch memory consumption can be an issue in some systems and keeping payload sizes relatively small ensures an optimal experience for most users. This limit can be modified if you want to take full advantage of particularly powerful hardware.