Pagepost vs Netlify Drop
Netlify Drop is genuinely good and genuinely free: drag a folder in and you get a working site on a real CDN. If you are publishing a site, use it. The friction shows up when what you actually have is one file and one recipient — you get a deploy to manage rather than a link to send.
Short answer
Netlify Drop is the better tool for a site. Pagepost is the better tool for a document.
Side by side
| Pagepost | Netlify Drop | |
|---|---|---|
| Best fit | A single HTML or Markdown file you want to send someone | A multi-file static site with assets and routes |
| Multiple files and assets | Single file only | Yes — full folder, any structure |
| Markdown rendering | Yes, rendered to a styled page | No — you would need a build step |
| Publish from an AI assistant | Yes, via the MCP connector | No |
| Revoke or expire a link | Yes, per link | Delete the deploy |
| View counts | Per link, built in | Analytics is a paid add-on |
| Custom domain | No | Yes |
| Cost | Free | Free tier, paid above it |
When Netlify Drop is the better choice
- You have more than one file — images, stylesheets, multiple pages, routes.
- You want a custom domain, redirects, or build hooks.
- The thing you are publishing is a site you will keep updating, not a document you are sending once.
Questions
Can I publish a whole folder to Pagepost?+
No. Pagepost is deliberately single-file: one HTML or Markdown document per link. If your page depends on separate CSS, JS or image files, either inline them into the one file or use a static host like Netlify.
Do AI assistants produce single-file pages?+
Usually yes. Claude artifacts, ChatGPT canvas HTML and similar output are typically one self-contained file with inline styles and scripts, which is exactly the shape Pagepost is built for.
Can I move a page from Pagepost to Netlify later?+
Yes. Your file is yours — download it from the dashboard and deploy it anywhere.