Overview
A project contains:- Shared label schema: Labels and attributes used across all tasks
- Quality settings: Validation and quality control configuration
- Tasks: Individual annotation jobs with uploaded data
- Organization: Optional workspace for team collaboration
Creating a Project
Using the Web UI
- Navigate to the Projects page
- Click Create new project
- Enter project details:
- Name: Descriptive project name
- Labels: Define your annotation schema (see Labels & Attributes)
- Bug tracker: Optional issue tracking URL
- Configure advanced settings (optional):
- Source storage: Cloud storage for importing datasets
- Target storage: Cloud storage for exporting annotations
- Click Submit to create the project
Using the REST API
Create a project with thePOST /api/projects endpoint:
Using the Python SDK
Install the SDK:Using the CLI
Install the CLI:Project Configuration
Organization Assignment
Projects can belong to an organization for team collaboration:Only organization members can access projects within that organization. Projects without an organization are personal projects.
Storage Configuration
Configure cloud storage for importing and exporting data:local: CVAT server storage (default)cloud_storage: AWS S3, Azure Blob, or Google Cloud Storage
Bug Tracker Integration
Link an external issue tracker:Project Properties
Key project attributes returned by the API:| Field | Type | Description |
|---|---|---|
id | integer | Unique project identifier |
name | string | Project name |
owner | object | User who created the project |
assignee | object | User assigned to the project |
status | string | Project status: annotation, validation, completed |
created_date | datetime | Creation timestamp |
updated_date | datetime | Last modification timestamp |
dimension | string | Task dimension: 2d or 3d |
organization_id | integer | Organization ID (null for personal projects) |
tasks | object | Summary of project tasks |
labels | object | Project label schema |
Best Practices
Design your label schema carefully
Design your label schema carefully
- Define all labels upfront before creating tasks
- Use consistent naming conventions
- Add attributes for important object properties
- Consider label hierarchies for complex scenarios
- Review Labels & Attributes guide
Organize with meaningful names
Organize with meaningful names
- Use descriptive project names: “Traffic Scene Detection Q1 2026”
- Include version numbers for iterative datasets
- Add date ranges or data source information
Configure quality settings early
Configure quality settings early
- Set up validation parameters at project creation
- Define quality thresholds before annotation begins
- Enable consensus annotation for critical tasks
- See Quality Control for details
Use organizations for team work
Use organizations for team work
- Create projects within organizations for collaboration
- Assign roles and permissions appropriately
- Configure shared cloud storage for large datasets
Next Steps
Managing Tasks
Create and manage annotation tasks within your project
Labels & Attributes
Configure labels, attributes, and annotation schemas
Quality Control
Set up validation workflows and quality metrics
API Reference
View complete API documentation