How to Deploy a Static Website on Cloudinary: A Quick Guide
Cloudinary is primarily known for image and video management, but its powerful CDN and media library can also host static websites. This tutorial walks you through deploying a static site—like HTML, CSS, and JS files—on Cloudinary for fast, global delivery without a traditional web server.
Before you start, have your static website files ready (index.html, assets, etc.) and a free Cloudinary account. The entire process takes less than 10 minutes.
1. Prepare Your Static Files
Ensure all file paths are relative (e.g., ./style.css or images/logo.png). Cloudinary serves files from a folder, so avoiding absolute paths prevents broken links. Also, rename your entry HTML file to index.html so Cloudinary can automatically serve it when the folder is accessed.
2. Create a Cloudinary Upload Preset
- Log into Cloudinary Console → Settings → Upload.
- Click “Add upload preset” and set Signing Mode to “Unsigned” (for public sites).
- Under “Incoming Transformation”, optionally add auto-format or quality optimization for media files.
- Save the preset name; you’ll need it later.
3. Upload Files via the CLI or Dashboard
Option A: Dashboard (manual) – Drag and drop your entire website folder into the Cloudinary Media Library. Create a new folder (e.g., my-site) and upload all files there.
Option B: CLI (recommended for automation) – Install the Cloudinary CLI cld (via npm). Run cld upload --folder my-site --preset your_preset_name ./* from your site’s root directory. This bulk uploads everything.
4. Get Your Live URL
Once uploaded, your site is accessible at: https://res.cloudinary.com/YOUR_CLOUD_NAME/image/upload/v1/FOLDER_NAME/index.html. Replace YOUR_CLOUD_NAME and FOLDER_NAME. You can use a custom domain or a shorter URL by enabling “Strict Transformations” or using Cloudinary’s /image/upload URL structure directly.
That’s it! Your static site is now served via Cloudinary’s global CDN. For production, consider adding a custom CNAME and HTTPS for a branded experience. This method is ideal for landing pages, documentation, or portfolio sites where server‑side processing isn’t needed.