For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
GuidesIntegrationsAPI ReferencesRelease notes
GuidesIntegrationsAPI ReferencesRelease notes
  • Introduction
    • Overview
    • Quick Start
    • Projects
    • Billing
  • Uploading
    • Overview
    • Uploading files with API
    • File analysis on upload
  • Optimization
    • Overview
  • Transformations
  • Delivery
    • Overview
    • On-the-fly operations
    • CDN settings
    • Proxy
  • Security
    • Overview
    • Validation and moderation
    • Signed uploads
    • Signed URLs
    • Unsafe content moderation
    • Malware protection
    • HIPAA workflows
  • Storage
    • Uploadcare storage
    • Cloudflare R2
    • Google Cloud Storage
    • Azure Blob Storage
  • File management
    • Overview
    • Managing files
    • File groups
    • Webhooks
    • Arbitrary file metadata
  • CLI
    • Overview
    • Configuration
  • Migration
    • Migration to Uploadcare
    • Migration from Filestack
Dashboard
LogoLogo
On this page
  • API keys
  • Public API key
  • Secret API keys
  • Settings
  • Team
  • Project settings
Introduction

Projects settings

Was this page helpful?
Previous

Billing

Next
Built with

The Uploadcare experience is centred around the concept of a project. Projects are separate environments with unique API keys, dedicated storage, and other settings.

You can create a few projects for one account. Information about all existing projects can be found on the Workspace tab.

Every project has detailed analytics.

We recommend creating at least two projects: for staging and the production environment.

We also recommend having different projects for different kinds of data: one serves your frontend assets, another for user-generated content, and one more for content that must be additionally secured with signed uploads and URLs.

API keys

We provide two kinds of API keys: public and secret.

Public API key

The main use of a YOUR_PUBLIC_KEY is to identify a target project for your uploads. Only public key is required when using most features of the Upload API (or its clients, such as the File Uploader).

Secret API keys

A YOUR_SECRET_KEY is required when using our REST API to manage files within a project or when implementing signed uploads. Generate as many secret API keys as you need to have precise control.

Settings

Every project can be configurable in its Dashboard.

Uploading settings:

  • Maximum file size
  • MIME type filtering
  • Malware protection rules
  • EXIF Metadata removal
  • Signed uploads
  • Custom OAuth for external uploading sources
  • Custom uploading CNAME

Storage settings:

  • File storing behavior
  • AWS S3 integration
  • Backup to S3 bucket

Delivery settings:

  • Auto WEBP/AVIF
  • Adaptive quality
  • Search engine indexing behavior
  • Signed URLs
  • Custom CDN CNAME
  • Proxy CNAME
  • Allowed domains for Proxy

Team

The account owner can add collaborators to their projects. Collaborators:

  • Have full access to project files.
  • Have access to this project’s settings (including secret keys).
  • Can’t invite new users to the project.
  • Can’t delete the project. Only the project owner can do that.
  • Don’t have access to the payment settings for that project.

Billing rules are inherited from the account owner; therefore, projects will be created for this account with the same limits as the owner, regardless of the plan that the collaborators are on.

If the invited user doesn’t have an Uploadcare account, they will be redirected to the signup page (they should use the same email address to which they were invited). The invitation link is valid for 24 hours.

Configure your team in the Team section.

Project settings

You can rename the project or delete it in the Project section of the Dashboard.