Files
Host a file, get a link that never changes
Files lives in the same workspace that delivers your images. Put files into a collection, make the collection public, and every file in it gets a permanent link you can paste anywhere — a deck, a press kit, a product image, a download.
Collections and links
- A collection is a folder. It is created restricted: nothing in it is served until you make it public.
- A public collection gives every file in it a link of the form
https://files.cdn.mn/f/<file-id>. Anyone who has the link can open the file — treat an open link like a published URL. - The link is the file’s id, not its name. Rename the file or move it to another collection and the link keeps working.
- Making a collection restricted again stops every link in it on the next request — typically within seconds, always within minutes. The dashboard shows a file as “still being removed” until its link has stopped.
Uploading
Open Files in your workspace, open a collection, and drop files in or choose them. Uploads run one after another and each file is checked before it is stored:
- Size: up to 25 MB per file, on every plan.
- Types: JPEG, PNG, WebP, AVIF and GIF images; PDF; Word, Excel and PowerPoint (the modern
.docx/.xlsx/.pptxformats) and OpenDocument files; zip archives. - Decided by content, not by name. What a file is gets read from its bytes. A renamed HTML file or executable is refused, and a PDF with junk in front of it is refused as well.
- Not accepted yet: SVG (it can carry script), the legacy Office formats (
.doc/.xls/.ppt, which can carry macros), and plain text or CSV. Convert an SVG to PNG or WebP; save a legacy Office file in its modern format.
Files are served with headers that tell browsers exactly what they are and never to guess, and documents that are not images or PDFs are offered as downloads rather than opened in the page.
Storage per plan
Each monthly plan includes a fixed amount of file storage. When the workspace reaches it, uploads pause until you delete something or move to a larger plan; existing files keep serving. Deleting a file frees its space right away. Pay-as-you-go has no cap: stored files draw down the credit at 0.5¢ per MB per month, prorated by the hour, and uploads pause when the credit is used up. Before the first collection, the workspace owner agrees that Files carries no malware, no content the workspace has no rights to, and nothing else the Acceptable Use Policy forbids; existing customers agree once on their next visit.
| Plan | File storage |
|---|---|
| Pay-as-you-go | Metered — 0.5¢ per MB per month, from your credit |
| Growth | 50 GB |
| Business | 250 GB |
| Video | 100 GB |
| Enterprise | Unlimited |
Early-stage startups get a paid plan free for a year through the startup programme, file storage included. The Files overview is the shorter, non-technical version of this page.
Deleting
Delete a file from its collection, or delete an empty collection. A deleted file’s link stops on the next request and the bytes are removed from storage within minutes. There is no trash: keep your own copy of anything you may need again.
Agents
An AI agent can do the same through the MCP server with the files:read, files:write, files:publish and files:share scopes: list collections and files, create a collection, upload a file (as base64, up to 8 MB per call), make a collection public or restricted, and run gated sharing end to end — list, create and revoke share links, read and publish the agreement, and read the access log. Publishing a collection, creating a share link and publishing an agreement are sensitive actions — each waits for your approval on the workspace’s Agents page unless you granted the agent autonomy for it. See the agent guide.
Gated sharing
On a collection page, create a share link and choose who can open it: anyone with the link, or only someone who verifies an email address with a one-time code first. A link can expire — after a preset number of days or at a date and time you choose, in your account’s timezone (set it once in Settings; every date on the dashboard shows in it) — be turned off at any time, and be view-only (no download button, and a direct download is refused). The collection’s access log records every file handed over — a download that cannot be logged is refused rather than served — along with verified addresses and file-list views, with a summary at the top. A link can also require an agreement: write the text on the collection page, publish it, and a recipient must read and accept it before the files are listed — the acceptance is recorded against the exact text they saw, and republishing asks everyone again. For a named audience, choose the invite-only gate: list the addresses that may open the link, each receives an email saying they have access, and anyone else who enters an address is told a code was sent and never receives one — the access log shows who tried. Invite more, resend, or remove someone under the link at any time. Keep confidential material in a restricted collection and share it only through a gated link. The access log exports as CSV (visitors, verified addresses, files opened).
What is next
Team members with roles.