> For the complete documentation index, see [llms.txt](https://docs.lumidb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumidb.com/archive-management/limits-and-storage.md).

# Limits and storage

How LumiDB counts storage and which limits apply to files, projects and plans.

### How storage is counted

LumiDB counts the size of the original data you import. If you import 100 GB of LAZ files, you use 100 GB of storage.

LumiDB also keeps your data in a format built for fast queries and streaming. That copy doesn't count toward your storage.

### File and project size

LumiDB has no limit on the size of a file or a project. The limit is the storage included in your plan.

### Export size

A single export can be at most 10 GB, or 4 GB for glTF. The export dialog shows the estimated size, and the export buttons are grayed out when a clip is over the limit. Draw a smaller area, or download the original files. See [Merging, cropping, and filtering datasets](https://docs.lumidb.com/explore-and-analyze/merging-cropping-and-filtering-datasets.md).

### Plans

Your plan decides how much storage you have and which features you can use. Contact <help@lumidb.com> if you need more storage or have questions about your plan.

### Large data

If you plan to import 2 TB or more, write to <help@lumidb.com> before you start. We can help you plan the import. See also [Importing data](https://docs.lumidb.com/import-data/importing-data.md) and [Supported formats and file requirements](https://docs.lumidb.com/import-data/supported-formats-and-file-requirements.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lumidb.com/archive-management/limits-and-storage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
