Smooth CDN delivers assets through a predictable and optimized request pipeline. Requests are resolved deterministically without hidden runtime logic.

• Resolve the requested user and project.
• Resolve the target version.
• Resolve the requested asset path.
• Apply format negotiation when supported (images, audio, video).
• Serve the asset with optimized cache headers.

Uploads, configuration, and access rules are managed outside the CDN layer. The CDN focuses purely on fast and predictable delivery.

Assets are delivered using stable and human-readable URLs.

Pattern

https://cdn.smoothcdn.com/<user-slug>/<project-slug>/<version>/<asset-path>

• <user-slug> — owner identifier
• <project-slug> — project identifier
• <version> — specific version or latest (applicable only if project type is versioned, skip for other types)
• <asset-path> — full relative file path

You can also specify custom subdomain for your project (available on paid plans only). Then Your URL will look like this:

https://<project-subdomain>.smoothcdn.com/<version>/<asset-path>

You can also list all available assets in project using following URL:

https://cdn.smoothcdn.com/<user-slug>/<project-slug>/<version>/list

Smooth CDN allows common web asset types. Unsupported file types are rejected at the delivery layer.

Allowed extensions

• Scripts: .js, .mjs
• Styles: .css
• Fonts: .woff2, .woff, .ttf, .otf
• Images: .png, .jpg, .jpeg, .webp, .avif, .svg
• Documents: .pdf, .md, .doc, .docx, .xls, .xlsx, .ppt, .pptx, .odt, .ods, .odp
• Data: .json, .txt
• Audio: .mp3, .ogg, .wav
• Video: .mp4, .mov, .avi, .webm, .mkv

Asset delivery and format optimization

Smooth CDN does not only store uploaded assets. The platform also prepares optimized variants and tries to serve the best available format for the current request while keeping the same stable asset URL.

• Images are optimized into .webp and .avif variants when possible.
• Audio files are optimized into .m4a variants when possible.
• Video files are optimized into .m4v variants when possible.
• Smooth CDN uses request information such as supported response formats to choose the best variant it can return from the same asset URL.

If you need the originally uploaded file instead of the optimized delivery variant, append ?original=1 to the asset URL.

https://cdn.smoothcdn.com/<user-slug>/<project-slug>/<version>/<asset-path>?original=1

Assets can be referenced directly in HTML, CSS, or JavaScript using CDN URLs.

<link rel="stylesheet" href="https://cdn.smoothcdn.com/user/project/app.css" />
<script defer src="https://cdn.smoothcdn.com/user/project/app.js"></script>

<img src="https://cdn.smoothcdn.com/user/project/logo.png" alt="Logo" />

You can also use the developer panel or the CLI command scdn get-snippet to generate a production-ready snippet for a selected asset.

Smooth CDN can optionally restrict access to assets. By default, assets are public and optimized for global delivery.

Token-based access

Require a token for asset delivery. Recommended for premium or private assets.

Authorization: Bearer <token>

https://cdn.smoothcdn.com/<user>/<project>/<version>/<asset>?t=<token>

Token-based access is intended for server-side usage and controlled distribution.

The CDN returns standard HTTP status codes for delivery errors.

• 404 Not Found — asset does not exist
• 403 Forbidden — access denied
• 415 Unsupported Media Type — file type is not allowed
• 429 Too Many Requests — rate limited
• 5xx — edge or internal failure