droppage

droppage

Drop an HTML file. Get a live link. Control who sees it.

droppage is a command-line tool that publishes a single HTML file to a live, shareable URL in one command — with access control that feels like sharing a document, not deploying a website. It is built for developers, analysts, and AI agents that produce HTML reports and need a URL without running a hosting stack.

$ droppage upload report.html

https://droppage.dev/p/k3x9qd2m

Website: droppage.dev · Source: github.com/Vilancer/droppage-cli

Install

Requires Node.js 22 or newer.

npm install -g droppage

droppage --version

Quick start

droppage login                    # magic link sent to your email

droppage upload report.html # prints the share URL on stdout

Open the printed link in any browser. That's it.

Commands

Run droppage --help for full option details.

Slugs from 0.2.1 on never start with -. If an older page's slug does (say -AbC12xYz9), put -- in front of it, with any options before the --: droppage expire -- -AbC12xYz9 never or droppage update --expires 7d -- -AbC12xYz9 report.html. The CLI prints the same hint when it happens.

Access modes

--password, --email, and --private are mutually exclusive. update never changes the access mode — it only swaps the HTML. When you are signed in to droppage.dev, your own protected pages open directly, without the password or email link.

Rules for uploads

• One .html or .htm file per upload; the file is validated before any network call.
• Inline your CSS, JS, and data. Relative asset paths other than images will not resolve. Local images referenced in are uploaded with the page (see below); sensitive images belong inline as data: URIs.
• Views shown by list count one unique visitor per page. Refreshes, reopening in the same browser, link previews from chat apps, and your own opens do not add views.
• Preview URLs (list --preview) never increment the view count.

Images

Images belong to a page. Reference local image files in your HTML (inside the HTML file's folder; ../ and absolute paths are ignored), with paths relative to the HTML file, and upload it:

<img src="chart.png">

$ droppage upload report.html

droppage: image chart.png → https://droppage.dev/i/AbCdEfGhIjKl.png https://droppage.dev/p/k3x9qd2m

upload finds the images, uploads them to that page, rewrites the links to https://droppage.dev/i/ . , then publishes. The image lines go to stderr; stdout is still only the page URL.

• update uploads any new local images, keeps the same URL for an unchanged image, and deletes the page's images the new HTML no longer uses.
• Besides , the CLI picks up local images in srcset on / (every candidate, descriptors kept), , and url(...) inside blocks (0.2.2+). Not picked up: style="..." attributes and .ico files.
• Deleting a page, or the page expiring, removes its images too. Images never outlive their page.
• Image budget per page by plan: Free 5 MB, Starter 20 MB, Builder 50 MB. Each image up to 4 MB. PNG, JPEG, GIF, WebP, AVIF, SVG. Image traffic counts toward your monthly bandwidth.
• Prefer small formats: WebP or AVIF for photos and screenshots, SVG for charts and logos (often several times smaller than PNG or JPEG). The CLI prints a tip on stderr when a PNG, JPEG, or GIF is over 300 KB.
• Images are public to anyone with the URL. A page's password, email, or private gate does not protect them. Keep sensitive images inline in the HTML as data: URIs instead.
• Advanced: droppage image upload --page adds images to an existing page and prints their URLs; droppage image list [--page ] [--json] shows them (--json prints {images:[{id,url,ext,content_type,bytes,name,created_at,page}], page?:{slug,used_bytes,limit_bytes}}); droppage image delete removes them.

Videos

Short product films (CLI 0.3.0+) are hosted exactly like images. Reference local MP4 or WebM files, and a poster image, in a :

<video autoplay muted loop playsinline poster="still.webp">

droppage upload page.html

stderr: droppage: image still.webp → https://droppage.dev/i/AbCdEfGhIjKl.webp

stderr: droppage: video film.webm → https://droppage.dev/i/MnOpQrStUvWx.webm

stderr: droppage: video film.mp4 → https://droppage.dev/i/YzAbCdEfGhIj.mp4

• Picked up: , (inside , and as before), and . Same folder rule as images.
• Each video up to 20 MB (20,000,000 bytes), checked by its file signature, not its name: MP4 (H.264 plays everywhere) and WebM (VP9). .mov and .mkv are refused; convert them first, e.g. ffmpeg -i in.mov -c:v libx264 -pix_fmt yuv420p -movflags +faststart -an film.mp4.
• Videos share the page's image budget (Free 5 MB, Starter 20 MB, Builder 50 MB per page), are pruned by update and deleted with the page, like images. Video traffic counts toward your monthly bandwidth.
• Served from https://droppage.dev/i/ .mp4|webm with HTTP Range support (206 Partial Content), so Safari, iOS and seeking work. Public to anyone with the URL, like images.
• No need to inline films as base64 any more. droppage image upload film.mp4 --page (or droppage media upload) adds a video to an existing page.

Expiry

Pages can expire. Nothing expires unless you set it, on any plan.

droppage upload report.html --expires 7d          # also 30m, 12h, 2w, or a date like 2026-12-31

droppage update report.html --expires never droppage expire 2026-12-31 # change it without re-uploading; never clears it

After expiry the page shows "This page has expired." (HTTP 410) to everyone, including you, and its images stop working. A daily cleanup then deletes the page and its images for good. droppage list shows an EXPIRES column (never or a date); list --json rows have expires_at (null means never).

Sharing reports and dashboards

droppage is a quick way to send an analysis to people who don't have your tools: a dashboard for your team, a weekly KPI or stakeholder report, a client deliverable, a notebook export. They open a link.

• Design it well. Agents should load Anthropic's frontend-design skill before building the page, so the report gets a deliberate look instead of a templated one. Claude Code: /plugin install frontend-design@claude-plugins-official; Codex, Cursor, and other agents: use its SKILL.md from anthropics/skills.
• Export one HTML file, up to 5 MB, with the data inside it: jupyter nbconvert --to html analysis.ipynb, Plotly's fig.write_html("report.html", include_plotlyjs="cdn"), Altair's chart.save("report.html"), or your own Chart.js / ECharts page. Scripts run, so interactive charts work, and chart libraries can load from a CDN.
• Pages run in a sandbox: localStorage, cookies, and same-origin requests are not available, so keep the data in the file rather than fetching it.
• Pick who sees it. --email cfo@example.com,ops@example.com for named people (Builder; manage them later with droppage recipients), --password for a group link (Starter and Builder), --private for a draft. On the Free plan, pages can be public or private, without a password or email list.
• Same link every week. droppage update report.html replaces the report and keeps the link and its access settings (Starter and Builder). Use --expires 30d for one-off deliverables.
• Views are people. droppage list --json shows view_count (unique visitors) and last_viewed_at for each report.

For agents and scripts

droppage keeps a strict stream contract so it is safe to call from automation:

• upload and update print only the URL on stdout, even when they upload images; image upload prints only the image or video URL(s); expire prints nothing on stdout.
• list --json, image list --json, recipients list --json, and quota --json print only JSON on stdout.
• Progress, warnings, prompts, errors, and the per-file droppage: image … → … / droppage: video … → … lines go to stderr.
• Non-zero exi