File type catalog

component.yml slots that bind to uploaded workspace Files carry a file_type: tag. The platform uses it to decide which uploaded File can fill a file_schema: input slot and to label what kind of File a generated_file_schema: output produces. The bind is refused unless the uploaded File's type is one of the values the slot declares. An input slot may accept several types by joining them with |; an output declares exactly one.

The values components reach for most often fall into a few groups: model artifacts (model, weights, onnx, mar, safetensors, checkpoint, tokenizer, lora, gguf), tabular and document formats (csv, tsv, excel, parquet, arrow, pdf, json, jsonl, yaml, toml, xml, html, markdown, text, srt, vtt), media (image, audio, video, mesh, point_cloud), and the generic numpy, faiss, archive, and binary. The full accepted set is larger — the CLI reference lists every value --type takes.

The most common mismatch is a Triton model repository uploaded as weights (it should be model), or a single ONNX file uploaded as model (it should be onnx).

The full per-value reference, the multi-type slot syntax, and the bind syntax live in the CLI:

ppl docs get file-api/file-typesCopy
ppl docs get file-api/file-schemaCopy
ppl docs get concepts/modelsCopy
ppl docs get flows/file-upload-and-bindingCopy

Related

• File schema
• File binding
• Models
• File upload and binding