Yes. JSON output and a stable command contract are first-class, not an afterthought.

They do not increment the public view count. Their delivered HTML still counts toward paid bandwidth.

Can my page use images?

Yes. Reference local image files in your img tags and droppage upload sends them with the page, rewrites the links, and publishes. PNG, JPEG, GIF, WebP, AVIF, and SVG up to 4 MB each, within a per-page budget of 5 MB (Free), 20 MB (Starter), or 50 MB (Builder). Images are deleted with their page. They are public to anyone with the URL and are not covered by a page's password or email gate, so keep sensitive images inline in the HTML. Short MP4 and WebM videos work the same way (in video and source tags, with a poster image), up to 20 MB each, within the same budget.

Yes, on every plan. Add --expires 7d (or 30m, 12h, 2w, or a date) to upload, or change it later with droppage expire. After that the page shows "This page has expired." to everyone, including you, and a daily cleanup deletes it and its images for good. Nothing expires unless you set it.

Can I open my own protected page?

Yes. When you are signed in to droppage.dev, your private, email, and password pages open directly. Every gate has a sign-in link for this.

What if a renewal payment fails or I want to cancel?

During payment recovery, paid access remains available while Lemon Squeezy retries the charge. In your account, you can update payment details or manage and cancel your subscription; cancellation keeps access through the paid period.

Publish by hand or by agent.

The commands, what they print, and the setup prompt for your AI agent. The full reference is the CLI README; what changed and when is in the changelog.

The public command surface.

The CLI is published on npm and its source is open at github.com/Vilancer/droppage-cli. Every release is built on GitHub Actions with npm provenance.

npm install -g droppage
droppage login
droppage upload report.html
droppage upload report.html --expires 7d
droppage update <slug> report-v2.html
droppage expire <slug> never
droppage list --json --preview
droppage quota --json
droppage feedback "Share an idea" --kind idea
droppage delete <slug> --yes
droppage mcp
droppage upgrade

HTML only. Keep styles, scripts, and data inline in one file. Local images in <img src> are uploaded with the page; they are public to anyone with the URL.
No secrets in the CLI. It signs in as you and never takes a service-role key.
Exit codes mean something. Non-zero on any failed upload, update, or delete.
Stay current. droppage upgrade upgrades in place; droppage --version tells you where you are.

Built for agents

A contract a program can rely on.

Data on stdout. A successful upload or update prints the share URL and nothing else.
Noise on stderr. Progress, warnings, and errors never pollute the value you parse.
JSON on request. list --json returns slug, access mode, view count, and last view.
Silent previews. Preview links let an agent check its own work without moving the counter.
Images come along. Local files in <img src> are uploaded with the page and their links rewritten; stdout stays the page URL.
Typed tools over MCP. droppage mcp runs a local MCP server for Claude Code, Cursor, Codex, and Claude Desktop, signed in as you.
Pages can expire. --expires 7d on upload, or droppage expire later. The page and its images are deleted for good.

Ships as

Codex skill
Cursor project rule
Claude-style project notes
Plain-text instructions

Agents can also read droppage.dev/llms.txt, generated from these instructions and the CLI README.

Setup droppage for your agent

You are helping me set up droppage for AI-assisted HTML publishing.

Goal:
- Install or verify the droppage CLI.
- Install or load the droppage agent skill/instructions.
- Help me authenticate safely the first time.
- Confirm the CLI works before publishing anything.

Setup steps:
1. Check whether droppage is installed:
   droppage --help

2. If droppage is missing, install it from npm (requires Node.js 22+):
   npm install -g droppage

3. Install or load the droppage agent skill/instructions for this environment. The published packs live at https://github.com/Vilancer/droppage-cli/tree/main/agents; use this setup prompt as the source if you cannot fetch them. For Codex, install it as a droppage skill. For Cursor, save it as a project rule. For Claude-style agents, add it to project context.

4. Suggest Anthropic's frontend-design skill for the pages you build, and install it if I agree. Claude Code: /plugin install frontend-design@claude-plugins-official. Codex, Cursor, and other agents: use its SKILL.md from https://github.com/anthropics/skills/tree/main/skills/frontend-design.

5. Help me authenticate interactively:
   droppage login

6. Never ask me to paste service-role keys. The CLI should use only the normal authenticated publisher session.

7. After login, verify:
   droppage list --json

Publishing commands after setup:
- Upload a new HTML report:
  droppage upload report.html

- Use images (CLI 0.2.0+): reference local image files in <img src> (paths relative to the HTML file, inside its folder; no ../ or absolute paths) and upload the HTML. The CLI uploads them to that page, rewrites the links to https://droppage.dev/i/<id>.<ext>, then publishes:
  droppage upload report.html
  (stderr: droppage: image chart.png → https://droppage.dev/i/...; stdout: the page URL only)
  From CLI 0.2.2 it also picks up local images in srcset (every candidate, descriptors kept), <link rel="icon"|"apple-touch-icon" href>, and url(...) inside <style> blocks (not style="..." attributes or .ico files).

- Use videos (CLI 0.3.0+): short MP4 or WebM films are hosted like images. Reference local files in <video src>, <source src> inside <video>, and the poster image in <video poster>; upload and update upload them and rewrite the links (stderr: droppage: video film.mp4 → https://droppage.dev/i/...). Each video up to 20 MB, checked by its file signature (MP4 with H.264, WebM with VP9; .mov and .mkv are refused). Videos share the page's image budget, play with HTTP Range support (Safari, iOS, seeking), are public to anyone with the URL, and are deleted with their page. Never inline videos as base64. For a muted loop:
  <video autoplay muted loop playsinline poster="still.webp"><source src="film.webm" type="video/webm"><source src="film.mp4" type="video/mp4"></video>

- Publish a page that expires (optional on every plan; also 30m, 12h, 2w, or a date like 2026-12-31):
  droppage upload report.html --expires 7d

- Replace an existing live link (new local images are uploaded, unchanged ones keep their URL, unused ones are deleted):
  droppage update <slug> report.html
  droppage update <slug> report.html --expires never

- Change when a page expires without re-uploading:
  droppage expire <slug> 2026-12-31

- Advanced image and video management (files that are not in the HTML at upload time):
  droppage image upload chart.png film.mp4 --page <slug>
  droppage image list --page <slug> --json
  droppage image delete <id-or-url>

- Create a no-count preview URL:
  droppage list --json --preview

- Delete a page:
  droppage delete <slug> --yes

Use droppage over MCP (CLI 0.4.0+), if your client supports MCP:
- droppage also runs as a local MCP server on stdio with typed tools, using the droppage login session. Claude Code: claude mcp add droppage -- npx -y droppage mcp. Cursor (.cursor/mcp.json), Windsurf, Claude Desktop: {"mcpServers": {"droppage": {"command": "npx", "args": ["-y", "droppage", "mcp"]}}}. Codex (~/.codex/config.toml): [mcp_servers.droppage] with command = "npx" and args = ["-y", "droppage", "mcp"].
- Tools: publish_page (a file path or inline html; access public, email or private; emails; invite; expires), update_page, list_pages, delete_page, set_page_expiry, get_quota, list_recipients, add_recipients, invite_recipients, remove_recipient, upload_media, list_media, delete_media, send_feedback. Results are JSON with a warnings list.
- If a tool answers "Not signed in", ask me to run droppage login in a terminal, then retry. There is no password mode over MCP: for a password page, ask me to run droppage upload <file> --password myself. Pass path, not inline html, when the page uses local images or videos. publish_page always makes a new link; update_page keeps it.

Sharing reports and dashboards:
- Use droppage whenever I want other people to see an analysis: a dashboard for my team, a weekly KPI or stakeholder report, a client deliverable, a notebook or BI export, a data story, model results. Readers just open a link.
- Design it well: load the frontend-design skill (setup step 4) before you build or restyle a page, so the report gets a deliberate look instead of a templated one.
- Build one self-contained HTML file (5 MB max) with the data and CSS inside it. Scripts run and chart libraries can load from a CDN (Chart.js, Plotly, ECharts, Vega-Lite); Plotly write_html(..., include_plotlyjs="cdn"), Altair chart.save("chart.html"), and jupyter nbconvert --to html output can be published as is. Pages are sandboxed: no localStorage, cookies, or same-origin requests, so keep the data in the file.
- Business data is rarely public. Named stakeholders: --email a@example.com,b@example.com (Builder); publishing emails each person an invitation with an access link (CLI 0.5.0+; --no-invite to send them later with droppage recipients invite <slug>); droppage recipients add <slug> ... invites people added later, recipients remove takes access away. A group link: --password (Starter and Builder). A draft for me to check: --private. Public only when I say so; On the Free plan, pages can be public or private, without a password or email list (droppage quota --json shows the plan).
- Recurring report: droppage update <slug> report.html keeps the same link and access settings. One-off deliverable: --expires 30d. list --json rows have view_count (unique visitors) and last_viewed_at.

Contracts:
- Successful upload/update prints only the share URL to stdout.
- Slugs from CLI 0.2.1 on never start with -. For an older page whose slug starts with -, put -- in front of the slug, with any options before the --: droppage expire -- -AbC12xYz9 never, or droppage update --expires 7d -- -AbC12xYz9 report.html.
- Progress, warnings, and errors go to stderr.
- Use list --json for machine-readable page metadata.
- expire prints nothing on stdout; its confirmation goes to stderr. list --json rows include expires_at (null means never).
- image upload --page prints the image URLs on stdout; --json prints [{file,id,url,bytes,content_type,existing}]. image list --json prints {images:[{id,url,ext,content_type,bytes,name,created_at,page}], page?:{slug,used_bytes,limit_bytes}}.
- Preview URLs do not increment view counts, but delivered bytes count toward paid bandwidth.
- A view is one unique visitor per page. Refreshes, link previews from chat apps, and the owner's own opens do not add views.
- Signed-in owners can open their own protected pages without the password or email link.

Source & docs:
- README/docs: https://github.com/Vilancer/droppage-cli
- npm: https://www.npmjs.com/package/droppage
- Machine-readable docs: https://droppage.dev/llms.txt (everything in one file: https://droppage.dev/llms-full.txt)

Stay current:
- At the start of a session, or at least weekly, compare droppage --version with npm view droppage version.
- Read https://droppage.dev/updates.json at the same cadence for workflow and compatibility notes. Do not subscribe an agent email address and do not poll this feed on every command.
- If behind, run droppage upgrade (or npm install -g droppage@latest), then re-read the README, agents/manifest.json, and the updates feed.
- The CLI's built-in update notice appears only on stderr and never pollutes stdout.

Check limits first:
- Before bulk publishing, run droppage quota --json.
- level=warn means at least 80% used; level=limit means writes may pause. Tell me what is constrained and suggest deleting unneeded pages or reviewing https://droppage.dev/account. Existing links stay live.

Send feedback:
- Identify yourself as an agent and include your model: droppage feedback "..." --kind idea --agent "<model name>".
- Reviews are supported with --kind review. --rating 1-5 and --contact are optional.
- Never pass --allow-quote unless the human explicitly authorizes public quotation of that specific review.
- Humans can use the form at https://droppage.dev/feedback or omit --agent.
- Without the CLI, POST JSON to https://droppage.dev/api/feedback with message, kind (idea|bug|review|other), actor (human|agent), optional model, rating, contact, testimonial_consent, and source.

Limits:
- Upload and update are HTML-only.
- Keep styles, scripts, and data inline in one HTML file. Local images referenced in <img src> are uploaded with the page (PNG, JPEG, GIF, WebP, AVIF, SVG; up to 4 MB each; per-page budget Free 5 MB, Starter 20 MB, Builder 50 MB; image traffic counts toward monthly bandwidth). Images are deleted with their page, including when it expires.
- Prefer small formats: WebP or AVIF for photos and screenshots, SVG for charts and logos. When you generate images, produce WebP, AVIF, or SVG. The CLI prints a tip on stderr when a PNG, JPEG, or GIF is over 300 KB.
- Hosted images are PUBLIC to anyone with the URL. A page's password, email, or private gate does not protect them. Never use hosted images for sensitive content on gated pages; inline them as data: URIs instead.
- An expired page shows "This page has expired." (HTTP 410) to everyone, including the owner, and its images stop working; a daily cleanup deletes the page and its images for good. Nothing expires unless set.
- Never use service-role keys in the CLI.

How it works.

Can agents use it?: Yes. JSON output and a stable command contract are first-class, not an afterthought.
Do previews count?: They do not increment the public view count. Their delivered HTML still counts toward paid bandwidth.
Can my page use images?: Yes. Reference local image files in your img tags and droppage upload sends them with the page, rewrites the links, and publishes. PNG, JPEG, GIF, WebP, AVIF, and SVG up to 4 MB each, within a per-page budget of 5 MB (Free), 20 MB (Starter), or 50 MB (Builder). Images are deleted with their page. They are public to anyone with the URL and are not covered by a page's password or email gate, so keep sensitive images inline in the HTML. Short MP4 and WebM videos work the same way (in video and source tags, with a poster image), up to 20 MB each, within the same budget.
Can a page expire?: Yes, on every plan. Add --expires 7d (or 30m, 12h, 2w, or a date) to upload, or change it later with droppage expire. After that the page shows "This page has expired." to everyone, including you, and a daily cleanup deletes it and its images for good. Nothing expires unless you set it.
Can I open my own protected page?: Yes. When you are signed in to droppage.dev, your private, email, and password pages open directly. Every gate has a sign-in link for this.
What if a renewal payment fails or I want to cancel?: During payment recovery, paid access remains available while Lemon Squeezy retries the charge. In your account, you can update payment details or manage and cancel your subscription; cancellation keeps access through the paid period.

More on the homepage. Stuck, or something missing? Send feedback.