> For the complete documentation index, see [llms.txt](https://docs.pinot.apache.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pinot.apache.org/build-with-pinot/ingestion/formats-filesystems.md). # Formats and Filesystems Match Pinot ingestion to the right input formats and deep-storage filesystems without overcomplicating the table design. Pinot supports several source formats and deep-storage choices. Pick these early, because they affect how segments are produced, moved, and recovered. ## Source formats Use the original format docs when you need the exact supported file types or loader behavior. The main landing page is [Supported Data Formats](/build-with-pinot/ingestion/formats-filesystems/pinot-input-formats.md). ## Filesystems and deep storage Choose the deep-storage backend that matches your operational environment. The detailed filesystem docs still live under [File Systems](/build-with-pinot/ingestion/formats-filesystems/file-systems.md). ## Keep it simple Do not mix format decisions with schema design. The schema says what the data means; the filesystem says where segments survive after Pinot produces them. ## What this page covered This page covered how source formats and deep storage fit into the ingestion design. ## Next step Read [Transformations and Aggregations](/build-with-pinot/ingestion/transformations-and-aggregations.md) if data needs cleanup or pre-aggregation before query time. ## Related pages * [Ingestion](/build-with-pinot/ingestion.md) * [Batch Ingestion](/build-with-pinot/ingestion/batch-ingestion.md) * [Stream Ingestion](/build-with-pinot/ingestion/stream-ingestion.md) * [Upsert and Dedup](/build-with-pinot/ingestion/upsert-dedup.md) * [Supported Data Formats](/build-with-pinot/ingestion/formats-filesystems/pinot-input-formats.md) * [File Systems](/build-with-pinot/ingestion/formats-filesystems/file-systems.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.pinot.apache.org/build-with-pinot/ingestion/formats-filesystems.md?ask=&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.