Skip to content
Back to

Supported formats

File Input nodes accept the extensions below by default. You can limit accepted types in the File Input node settings. Parsed tabular data becomes Apache Arrow datasets on the workflow engine (see Storage and processing).

Extension reference

Section titled “Extension reference”
Extension Category Processing
.csv Tabular and spreadsheets Parsed in-browser or on the workflow engine into Arrow datasets. Excel formats use server-side conversion.
.tsv Tabular and spreadsheets Parsed in-browser or on the workflow engine into Arrow datasets. Excel formats use server-side conversion.
.psv Tabular and spreadsheets Parsed in-browser or on the workflow engine into Arrow datasets. Excel formats use server-side conversion.
.xls Tabular and spreadsheets Parsed in-browser or on the workflow engine into Arrow datasets. Excel formats use server-side conversion.
.xlsx Tabular and spreadsheets Parsed in-browser or on the workflow engine into Arrow datasets. Excel formats use server-side conversion.
.json Structured data JSON and XML load as structured records for downstream transforms.
.xml Structured data JSON and XML load as structured records for downstream transforms.
.fix Financial data FIX, SWIFT MT / MT940, and OFX/QFX parsed via the platform file-parser pipeline.
.swift Financial data FIX, SWIFT MT / MT940, and OFX/QFX parsed via the platform file-parser pipeline.
.mt940 Financial data FIX, SWIFT MT / MT940, and OFX/QFX parsed via the platform file-parser pipeline.
.ofx Financial data FIX, SWIFT MT / MT940, and OFX/QFX parsed via the platform file-parser pipeline.
.qfx Financial data FIX, SWIFT MT / MT940, and OFX/QFX parsed via the platform file-parser pipeline.
.pdf Office and PDF PDF and office documents route through Docling on the workflow engine for structure, tables, and text extraction.
.docx Office and PDF PDF and office documents route through Docling on the workflow engine for structure, tables, and text extraction.
.pptx Office and PDF PDF and office documents route through Docling on the workflow engine for structure, tables, and text extraction.
.txt Text, markup, and captions Plain text and markup sources for structured extraction and downstream transforms.
.md Text, markup, and captions Plain text and markup sources for structured extraction and downstream transforms.
.markdown Text, markup, and captions Plain text and markup sources for structured extraction and downstream transforms.
.html Text, markup, and captions Plain text and markup sources for structured extraction and downstream transforms.
.htm Text, markup, and captions Plain text and markup sources for structured extraction and downstream transforms.
.adoc Text, markup, and captions Plain text and markup sources for structured extraction and downstream transforms.
.asciidoc Text, markup, and captions Plain text and markup sources for structured extraction and downstream transforms.
.asc Text, markup, and captions Plain text and markup sources for structured extraction and downstream transforms.
.tex Text, markup, and captions Plain text and markup sources for structured extraction and downstream transforms.
.latex Text, markup, and captions Plain text and markup sources for structured extraction and downstream transforms.
.vtt Text, markup, and captions Plain text and markup sources for structured extraction and downstream transforms.
.png Images Raster images for OCR and document-ingest workflows via Docling.
.jpg Images Raster images for OCR and document-ingest workflows via Docling.
.jpeg Images Raster images for OCR and document-ingest workflows via Docling.
.tif Images Raster images for OCR and document-ingest workflows via Docling.
.tiff Images Raster images for OCR and document-ingest workflows via Docling.
.bmp Images Raster images for OCR and document-ingest workflows via Docling.
.webp Images Raster images for OCR and document-ingest workflows via Docling.

FIX parsing

Section titled “FIX parsing”

FIX (Financial Information eXchange) log files load through the same File Input path as other structured imports.

  • One row per message - each FIX message becomes one workflow row.
  • Delimiters - SOH (ASCII 1), pipe (|), and escaped \x01 field separators are accepted in log files.
  • Field names - standard FIX tags map to readable column names such as MsgType and SenderCompID. Unknown tags keep the numeric tag; duplicate tags can appear as arrays.
  • Message boundaries - messages are recognised from 8=FIX. through the 10= checksum field.
  • Structured import - FIX rows are treated as already structured (one row per message). The importer does not suggest subgrid flattening for FIX sources.

Related finance formats on File Input: SWIFT (.swift, .mt940) and OFX/QFX use separate parsers in the same package. FIX round-trip export is supported on Egress via Save File Export.

Section titled “Related documentation”