Cromo uses different file paths for Knowledge ingestion and active work. Choose the destination based on what the file should become.
Limits by destination
Supported Source extensions
The Sources ingestion pipeline accepts:
The extension is checked before Cromo creates a Source record.
Choose the correct destination
Use Sources when the file should:
- support cited answers;
- produce proposed Knowledge;
- preserve evidence and provenance;
- remain part of the Project’s information base.
Use a chat attachment when the file is temporary context for one conversation.
Use team files for a generated report, CSV, draft, or other Project artifact that should be previewed, downloaded, or reused. Save a team file to Sources later if it becomes authoritative evidence.
Use a Workflow file input when a run definition explicitly asks the operator to supply a file.
Troubleshooting
Unsupported file type
Convert the file to a supported format without discarding important structure. For proprietary formats, PDF is often suitable for reading while CSV or XLSX is better for tabular data.
File is too large
Split the document at a meaningful boundary, such as chapter, reporting period, or business unit. Give each part a descriptive title so citations remain understandable.
Scanned content is hard to read
Use a higher-quality scan, correct page rotation, and confirm text and tables are legible before uploading.
Processing fails
Check the extension, file integrity, encryption or password protection, and size. Retry the Source after correcting the issue.
For Knowledge quality, a smaller authoritative file is usually better than a large archive containing duplicates and obsolete drafts.
