Overview
Artifacts are files produced by your crew during a run. Crewship automatically:- Collects files from a standard directory
- Stores them durably
- Makes them accessible via API and Console
Producing Artifacts
Standard Directory
Write files to/app/artifacts/ in your crew:
CrewAI Output Files
Use theoutput_file parameter in tasks:
tasks.yaml
Multiple Artifacts
Produce as many files as needed:Accessing Artifacts
Via CLI
Via API
Via Console
- Open the Console
- Navigate to your run
- Click the Artifacts tab
- Click any artifact to preview or download
Artifact Events
When an artifact is produced, an event is emitted:Supported File Types
Any file type is supported. Common types include:| Type | Extensions | Use Case |
|---|---|---|
| Text | .md, .txt, .csv | Reports, logs, data |
| JSON | .json | Structured data |
| Documents | .pdf, .docx | Formatted output |
| Images | .png, .jpg, .svg | Charts, screenshots |
| Archives | .zip, .tar.gz | Bundled outputs |
Size Limits
| Limit | Value |
|---|---|
| Single artifact | 100 MB |
| Total per run | 500 MB |
| Retention | 30 days |
Need larger limits? Contact us for enterprise plans.
Organizing Artifacts
Use subdirectories for organization:Best Practices
Use descriptive names
Use descriptive names
Name files clearly:
quarterly_report_2024Q1.md not output.mdInclude metadata
Include metadata
Add timestamps or run info to filenames when helpful:
Use appropriate formats
Use appropriate formats
- Markdown for human-readable reports
- JSON for structured data
- CSV for tabular data
- PDF for formatted documents
Compress large outputs
Compress large outputs
For many files, create a zip archive: