Portfolio Asset Hosting
Portfolio Asset Hosting on a Fast Global CDN
Host portfolio images, videos, and PDFs on a fast global CDN. One link per asset, pay only for what you use.
A portfolio is a performance pitch — and a hero image that takes four seconds to paint from a sluggish origin undercuts the work before anyone sees it. The usual hacks each have a flaw: committing full-resolution photos to a Git repo on GitHub Pages bloats the repo and serves from a non-CDN origin; stuffing a showreel onto a cheap VPS means you eat the bandwidth and reprovision when a post catches fire; embedding YouTube for video drags in their player chrome and recommendations. files.link is purpose-built for the assets a portfolio actually ships: high-res photography, MP4 showreels and motion pieces, case-study PDFs, 3D GLB models, and SVG logos, all served from a global CDN so the visitor in Sydney loads as fast as the one in São Paulo.
You can drag files into the dashboard, or — for agencies regenerating asset sets — drive uploads from a script via three REST calls (POST /v1/files/{folderId} → PUT the presigned URL → POST /v1/files/confirm-upload with {ids:[...]}), persist the returned CDN URLs, and drop them straight into a Next.js, Astro, Framer, or hand-rolled HTML site. The decoupling is the real win for working creatives: updating a single project image doesn't require a full site rebuild and redeploy the way a static-site-committed asset does — you replace the file and the new bytes flow through the CDN.
For an agency managing many clients, organize each client's media under its own folder, keep public-facing pieces on permanent public URLs, and put unpublished or NDA work behind private files served via signed URLs so a draft case study never leaks via a guessable path. Billing is prepaid credits debited by storage and delivery, which matters the day a piece gets shared widely: you'll see bandwidth usage rise, but there's no surprise overage invoice, and you can set a low max-storage cap in the dashboard as a guardrail.
Practical tips that keep a portfolio snappy: export photography to optimized WebP at the few widths your layout uses and reference them with srcset; compress showreels with ffmpeg before upload so a two-minute reel isn't a 400MB download; and flatten case studies to a single PDF rather than a zip of pages. files.link doesn't restrict by extension, so the same account handles every asset class your portfolio touches.
Benefits With No Complexity
Global CDN delivery
Edge-cached worldwide
Signed-URL security
What You Get
Unlimited files
Unlimited storage
Public + Private storage
CDN ready links
Prepaid credits
More coming soon
How files.link Works
1. Upload
2. Copy
3. Use Anywhere
Why Developers Choose files.link
A Better Way to Store & Deliver Files
| GitHub Pages (committed assets) | Personal VPS | files.link | |
|---|---|---|---|
| Global CDN delivery | |||
| Update one asset without a redeploy | |||
| REST API for batch upload automation | |||
| Private (signed-URL) draft/NDA assets | |||
| Prepaid credits (no bandwidth surprise bill) |
Calculate Your Needs
Storage
Egress
CDN Bandwidth
Host Portfolio Assets
- Global CDN delivery
- Edge-cached worldwide
- Signed-URL security
- Unlimited files
- Unlimited storage
- Public + Private storage
- No subscription — prepaid credits keep spend predictable