Features for one asset workflow.

Smooth CDN helps you upload files, optimize them automatically and share CDN-ready URLs from the tools your team already uses.

How Smooth CDN works

Three simple steps cover the main path from file to URL.

Upload assets

Add images, PDFs, frontend files and media to one Smooth CDN project.

Start from the web app, desktop sync, CLI or API.

Optimize automatically

Smooth CDN prepares lighter assets without adding another manual optimization step.

Best for images, documents, styles, scripts and media-heavy pages.

Share optimized URLs

Copy stable CDN URLs into websites, apps, emails, CMS fields or marketing material.

Use one URL workflow across technical and non-technical teams.

Original asset

Optimized for web

Asset optimization

Smooth CDN does more than compress files. It prepares the best web-ready formats for each supported asset type, so files are easier to serve on modern websites and apps.

Use this when you want lighter assets and better delivery formats without maintaining a separate optimization toolchain.

$ scdn init
$ scdn push
assets published

CLI publishing

Publish assets from local development, release scripts or CI/CD jobs with the Smooth CDN CLI.

Use this when asset publishing should move with your deployments.

Local folder syncs to optimized URLs

Desktop App

Sync local folders with Smooth CDN Connect when assets live on a designer, marketer or content team's computer.

Use this when manual uploads slow down day-to-day file work.

POST /assets
200 optimized_url

REST API

Send assets to Smooth CDN from your backend, internal tools or custom publishing workflow.

Use this when uploads need to happen inside your own product logic.

WP Media Assets

CDN URL

WordPress integration

Connect WordPress uploads to Smooth CDN so media can be optimized and delivered from CDN URLs.

Use this when WordPress should stay the publishing interface.

Media Library Assets

CDN URL

Strapi integration

Use the Strapi plugin to move media uploads into an optimized asset workflow.

Use this when Strapi is the editing layer for frontend content.

1.0.0released
1.1.0preview
latestactive

Versioned assets

Group files into versions when releases need predictable asset sets.

Use this when rollouts, previews or rollback paths matter.

access token
logged-in users

Protected delivery

Mark selected assets as protected when they should not be publicly downloadable by default.

Protected assets can be delivered with an access token or to logged-in users who have access to the project.

Invite collaborator
Access assets
Manage assets

Collaborators

Invite other people to a Smooth CDN project so they can access or manage files with their own account.

Use this when asset work is shared across teammates, clients, developers, designers or content teams.

Supported assets

Keep common project files in the same workflow.

Images
PDF
JavaScript
CSS
SVG
Fonts

Build one workflow for your assets.

Start with uploads and optimized URLs. Add CLI, desktop sync, API, integrations, protected delivery or collaborators when the workflow needs them.