---
date: 2026-07-08
title: "Parquet exports to blob storage"
description: Scheduled blob storage exports can now be written as Apache Parquet files. Parquet is the default for new integrations and configurable via the public API.
author: Niklas
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the current documentation (https://langfuse.com/docs) and the API/SDK reference (https://api.reference.langfuse.com).

Scheduled blob storage exports to S3, GCS, and Azure can now be written as **Apache Parquet** files — available to all projects and the new default for new integrations. Parquet is a columnar binary format that loads directly into warehouses and query engines like BigQuery, Snowflake, ClickHouse, or DuckDB, with no CSV parsing or JSON casting step:

- **Query exports in place.** Point DuckDB or Athena at your bucket and query the files directly — column pruning and predicate pushdown work out of the box.
- **Skip the staging schema.** Parquet files carry typed columns, so warehouse loads don't need per-field cast logic like text formats do.
- **Smaller files without gzip.** Parquet is compressed by the storage engine itself; the gzip option doesn't apply.

Select **Parquet** under **Project Settings → Integrations → Blob Storage**, or set it programmatically: the `fileType` field on [`GET`/`PUT /api/public/integrations/blob-storage`](https://api.reference.langfuse.com/#tag/blobstorageintegrations) now accepts `PARQUET` alongside `CSV`, `JSON`, and `JSONL`. Existing integrations keep their configured format.

Parquet observation exports do not include the per-unit model price columns (`input_price`, `output_price`, `total_price`). These columns snapshot model definition prices at export time and may be deprecated in the future — use `cost_details` and `total_cost` for cost data, which are included in every file type. Trace and score exports are identical across all file types. See the [Export Field Reference](/docs/api-and-data-platform/features/blob-storage-export-fields#parquet-exports) for details.

## Learn more

- [Export to Blob Storage](/docs/api-and-data-platform/features/export-to-blob-storage)
- [Export Field Reference](/docs/api-and-data-platform/features/blob-storage-export-fields)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2026-07-08-parquet-blob-storage-exports.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.