---
schema_version: "1"
id: 61f5d8dae4f532bece89c2b218913b4ff6a200e670744b447defebd3e8a93416
title: Supported File Formats in Data 360
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_supported_file_formats.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_supported_file_formats.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: fbedfc8696374828d3b06dcb5d6dddfce000452f4435626112369a64b3efb611
description: Data 360 supports various files and compression formats for your data stream sources.
products:
  - Data 360
release: "264"
---
# Supported File Formats in Data 360

Data 360 supports various files and compression formats for your data stream sources.

## Supported File Formats

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_important.png)

Important We recommend you refer [Data 360 Limits and Guidelines](https://help.salesforce.com/s/articleView?id=data.c360_a_limits_and_guidelines.htm&release=264.0.0&type=5 "Guidelines define best practice recommendations to optimize your adoption of Data 360 for best performance. Limits are boundaries beyond which features are unavailable, performance is throttled, or usage billing charges are applied. Since Data 360 is built to scale, some limits can be adjusted to meet your business needs. Work with your account executive to find a solution that meets your goals.") to know the applicable file limitations.

Data 360 supports these file formats:

- Delimited text files such as CSV files.
- Parquet files when data is ingested from Amazon S3, Google Cloud Storage, Microsoft Azure Storage, SFTP.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note You must use ASCII characters in text fields such as file name, wildcard, directory name, or formula syntax editor. UTF-8 sometimes contains non-ASCII characters that aren’t guaranteed to work properly. Also, don't use `:`(colon) and `'` (single quote) in file names and formulas.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note Files containing newline characters and multiline text columns are not supported.

## Supported File Formats for Unstructured Data

Data 360 supports several file formats for unstructured data and search index configurations. For a complete list, see [Unstructured Data File Formats and Connectors](https://help.salesforce.com/s/articleView?id=data.c360_a_unstructured_data_connect.htm&release=264.0.0&type=5 "Data 360 supports multiple file formats and connector types for unstructured data.").

## Supported Delimiters

Data 360 supports these content delimiters for text files:

- `,` (comma)
- \\t (tab)
- `|` (pipe)
- `;` (semicolon)
- `^` (caret)
- `¦` (broken pipe)
- \\u0001

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note Data 360 automatically evaluates the ingested files and determines the delimiter. We recommend using double quotes around values in a file to ensure the system detects the correct file delimiter.

## Supported File Compression Formats

Data 360 supports these compression formats for CSV files:

- GZ
- ZIP

Data 360 supports these compression formats for the data in the Parquet files:

- GZ
- ZIP
- NONE
- SNAPPY
- ZSTD

## Ingestion of Parquet Files

Data 360 supports these parquet data types and they’re converted to the corresponding Data 360 data types. If a parquet file contains a data type that's not supported in Data 360, the column is ignored and not ingested. You can view the unsupported fields when configuring the data stream in the New Data Stream page. You can also see the unsupported data types in the New Source Fields page when adding a source field. To ingest an unsupported data type. convert it to a Data 360 supported datatype in the source parquet file.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note \* Indicates a primitive data type in Parquet files.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d82860e197">Parquet Data Type</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d82860e200"><span>Data 360</span> Data Type</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">STRING</td>

            <td data-label="Data 360 Data Type" class="slds-cell-wrap" rowspan="3" style="vertical-align:top;" headers="d82860e200 ">Text</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">ENUM</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">UUID</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">BOOLEAN*</td>

            <td data-label="Data 360 Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e200 ">Boolean</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">DATE</td>

            <td data-label="Data 360 Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e200 ">Date</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">TIMESTAMP</td>

            <td data-label="Data 360 Data Type" class="slds-cell-wrap" rowspan="2" style="vertical-align:top;" headers="d82860e200 ">Datetime</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">INT96*</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">DECIMAL with 38 precision, 18 scale</td>

            <td data-label="Data 360 Data Type" class="slds-cell-wrap" rowspan="6" style="vertical-align:top;" headers="d82860e200 ">Number</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">DOUBLE*</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">FLOAT</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">INT</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">INT32*</td>

          </tr>
          <tr class="">
            <td data-label="Parquet Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d82860e197 ">INT64*</td>

          </tr>
        </tbody>
      </table>

Data 360 supports the following encoding formats for parquet files:

- Run-length encoding (RLE) Dictionary
- Plain Dictionary