Release notes

Uploadcare REST API v0.7 now supports file search and file tagging.

File search (POST /files/search/) supports:

• Full-text, exact, and fuzzy queries across filename, metadata, and MIME type
• Tag, date, size, and image type filters
• Pagination up to 1000 results with highlighted matched tokens

Signed URLs are now available on all plans, including free, and can be configured directly from project settings.

• Every project now has a dedicated secure subdomain ({subdomain}.s.ucarecd.net) that requires signed requests.
• Signing secrets can be generated from Settings → Delivery → CDN domain names in the dashboard.
• Up to two signing secrets can be active at the same time to support key rotation.
• Projects using a legacy ucarecdn.com domain must disable it to fully close unsigned access. This action is irreversible.
• Projects using custom CNAMEs are unaffected — existing setups continue to work without any changes.

Adaptive bitrate streaming now supports configurable codec and resolution settings at the project level.

Previously limited to three fixed resolutions (360p, 720p, 1080p) with H.264 only, you can now configure:

• Two codecs: H.264, H.265, or both per resolution
• Eight resolutions: 240p, 360p, 480p, 576p, 720p, 1080p, 1440p, 2160p
• Up to 16 rendition combinations
• Lower-resolution H.264 renditions are now up to 2x cheaper

The CLI can now download files from the Uploadcare CDN to the local filesystem.

$
# Download a single file
$
uploadcare file download <uuid> --output ./photo.jpg
$
$
# Mirror all stored files into ./backup with 8 parallel workers
$
uploadcare file list --page-all --stored true --json uuid \
>
  | uploadcare file download --from-stdin --output-dir ./backup --parallel 8

Adaptive bitrate streaming (ABS) is now easier to test and use on the Free plan.

Several changes were introduced to remove practical limitations and allow meaningful evaluation with real content:

• Maximum file size on the Free plan increased from 10 MB to 500 MB
• Upload restrictions for non-image file types removed
• The default demo project now includes video, document, and image examples

A public Plugin API is now available for extending the File Uploader with custom upload sources.

This allows developers to:

• integrate internal media libraries or proprietary storage
• add custom tabs to the uploader interface
• embed additional content sources directly into the upload flow

Adaptive bitrate streaming (ABS) is now available on all plans.

ABS is enabled by default for new projects. Existing projects can enable it in project settings if needed.

This change removes previous plan-based restrictions, making it easier to integrate adaptive video delivery into your product.

The Uploadcare CLI is now available as a non-interactive interface for working with the platform from the terminal.

It is designed for automation and scripting workflows, including:

• running file operations in CI/CD pipelines
• processing files in bulk without building integrations
• automating repetitive tasks without using the dashboard or SDKs
• integrating Uploadcare into AI agent workflows

Users can now schedule a plan downgrade from the Billing page.

Downgrades take effect at the end of the current billing cycle, allowing users to retain access to their current plan until the period they have already paid for ends.

The Billing page now shows:

Project search and sorting are now available on the Workspace page and in the project switcher dropdown.

You can now:

• search projects by name
• sort projects by Newest, Oldest, A–Z, or Z–A

The API Keys page has been updated to improve key management.

Added:

• optional names for secret keys
• creation date visibility for secret keys

These changes make key identification and rotation easier.

You can now select multiple files in the Files page using Shift-click.

This allows selecting a range of files in the list for bulk operations such as delete.

The EXIF Metadata removal feature allows users to remove metadata from images during the upload process.

When this feature is activated in the Dashboard, all newly uploaded images will be stripped of EXIF metadata, ensuring enhanced privacy and security. It doesn’t affect images that have already been uploaded before enabling the setting.

A new Optimize videos section has been added to Get started, helping users enable Adaptive Bitrate Streaming for improved playback.

The guide explains how adaptive delivery works, includes example videos, and provides ready-to-use configuration for UC Video or any custom player.

The Text overlay CDN operation now supports multiple font families and styles.
Previously only the default DejaVu was available. You can now choose among:

• DejaVu (default)
• DejaVuMono
• DejaVuSerif
• Noto
• NotoMono
• NotoSerif

Use the -/font/ operation to configure weight, style, size, color, and family,
then apply -/text/.../. See examples and parameters in the docs.

We’ve implemented enhanced security measures for trial accounts to provide a safer environment while you explore Uploadcare’s features. These measures help protect both our platform and your applications from potentially malicious files.

Trial accounts have full access to all common file types for web development, content creation, and document management, including:

• Images: All standard formats (JPEG, PNG, GIF, WebP, SVG, etc.)
• Videos: All popular formats (MP4, WebM, MOV, AVI, etc.)
• Audio: All standard formats (MP3, WAV, FLAC, OGG, etc.)
• Documents: PDFs, Office documents, text files, etc.
• Fonts: TTF, OTF, WOFF, WOFF2, etc.

• For developers integrating with our API the change is transparent and doesn’t require changes to your integration code.
• Attempts to upload restricted file types will result in a fileTypeForbiddenError error in Upload API.
• Malware protection works independently of the file type restrictions and is not affected by this change.

Now, Adaptive quality is enabled by default in all newly created projects. You can manage the Adaptive quality settings in the Dashboard.

https://app.uploadcare.com/projects/-/settings/#delivery

Effective September 2025.

New projects use only personal subdomains on *.ucarecd.net. Existing projects continue to use ucarecdn.com, with subdomains available in the Delivery tab of project settings. We have started implementing unique CDN subdomains for each project, replacing the generic https://ucarecdn.com/ domain. The default CNAME has been updated to use a subdomain in the format https://:subdomain.ucarecd.net/, where each project is assigned a unique subdomain (replacing the :subdomain).