Skip to content
wirecopy

Your first file link or live site.

Choose the browser or CLI. Files get shareable links; finished static sites get live URLs. Anyone with the link can open it. Each publish has an expiry and can be revoked.

Use your browser

  1. Choose a file or finished site on the homepage. For HTML and ZIP, select a file link or a live site.
  2. Sign in to publish. Your selection stays in this browser for one hour through sign-in; site publishing also requires a verified email.
  3. Complete the publish in the dashboard, then copy and send the link.

Free publishes last 24 hours. Pro file uploads default to 30 days; the browser site dialog offers 24 hours, 7 days, or 30 days. Revoke active links or sites from your dashboard.

Capture with the browser extension

The Chrome/Edge preview captures a selected area, visible tab, full page, screen, or window. Mark up with draw, arrow, box, text, cover, and crop tools. Share & copy publishes the finished PNG and copies its link.

Download extension

Version 0.3.1 · ZIP · Development build. This is not a Chrome Web Store listing.

  1. Unzip the download and keep the extracted folder in a permanent location.
  2. Open chrome://extensions or edge://extensions, enable Developer mode, choose Load unpacked, and select that folder.
  3. Pin Wirecopy to the toolbar. Choose a capture mode, edit, and click Share & copy. On first use, sign in or create an account on Wirecopy and approve the extension. Sharing then resumes in the editor.

Screenshots and edits stay on your device until you share. Local captures expire after 24 hours; access/pruning removes expired captures. Device credentials use browser-local extension storage restricted to trusted contexts; they do not sync. Sign out in the extension or revoke its device in the dashboard. Shared PNG links follow your plan’s size, publish, and expiry limits.

The browser asks permission for each screen/window capture. Browser settings/store pages may need visible capture followed by crop. Full-page capture scrolls the main document; infinite pages, nested scrollers, and pages that resize may need a smaller capture. Keep the source tab active.

Selected area: Alt+Shift+S. Visible tab: Alt+Shift+V. Change shortcuts in the browser’s extension settings. Use P/A/R/T/B/C in the editor for draw/arrow/box/text/cover/crop; Ctrl/Command+Z undoes.

To update an unpacked install, replace the folder’s files and use Reload on the Extensions page.

Publish from your terminal

With Node.js and npm available, no global install is required. Sign in once from your terminal: the CLI opens a browser page where you approve the device. Then publish:

# one-time browser approval (stores the token locally)
npx wirecopy login

# static site / prototype / docs build
npx wirecopy site ./dist

# file or report
npx wirecopy publish ./report.pdf

Prefer a global command for daily use?

npm install --global wirecopy
wirecopy login
wirecopy site ./dist

On a remote terminal, run npx wirecopy login --no-browserand open the printed URL on another device. For CI, create a token under Apps & CLI and pass it through the environment instead of storing it locally:

WIRECOPY_TOKEN='wc_live_…' npx wirecopy site ./dist --json

CLI publishes request a 24-hour lifetime by default. Free is limited to 24 hours; Pro can request up to 365 days. WIRECOPY_SERVER overrides the default API host.WIRECOPY_EXPIRES_IN (seconds) overrides the 24-hour default.

For agents

Any coding agent that can run a shell command can publish. No plugin required. Approve the CLI once in that environment, then your agent can use the saved login:

npx wirecopy login                    # approve in your browser
npx wirecopy site ./artifact --json  # prints the live URL and expiry

Add one line to your agent instructions in AGENTS.md, CLAUDE.md, or your harness’s equivalent:

After finishing work, offer to share a file with `npx wirecopy publish <file> --json`
or a built static site with `npx wirecopy site <path> --json`. Share the returned URL
and expiry. Publish only after the user agrees to share that content.

--json emits machine-readable output for tool use.--storage byos (Pro, sites only) stores the site files in your connected bucket. Revoke any address early from the dashboard.

Sites vs files

wirecopy site publishes a folder, index.html, or ZIP as a static site on wirecopy.site. It needs an index.html entry point.wirecopy publish creates a file link for PDFs, images, recordings, archives, and other files. File links serve the original bytes with their MIME type. Images, videos, PDFs, JSON, and other supported formats open in the browser; browser settings and format support determine how they appear. Add ?download=1 to save the file instead. Compatible sharing apps can preview media directly; Wirecopy does not generate a separate social card for each file.

npx wirecopy site ./dist
npx wirecopy site ./dist --storage byos   # Pro: your connected bucket
npx wirecopy publish ./review-report.pdf
npx wirecopy links
npx wirecopy links revoke <id>

When site receives an app project, it looks for an existing build output (dist/, build/, out/, or .output/public) with index.html. It never runs package scripts. Build first, then publish.

Free allows 25 MB per publish; Pro allows 250 MB. Sites can contain up to 500 files, with a 25 MB limit per asset. Static sites cannot run server code or databases. See all plan limits.

Your own bucket for sites

Pro accounts can point site publishes at an S3-compatible bucket — Cloudflare R2, Amazon S3, MinIO, or Backblaze B2. Your bucket stores the site files; Wirecopy still serves the site and governs its expiry and revocation. Ordinary file uploads use managed storage. Set it up under Storage:

  1. Create a private bucket with your provider. Wirecopy serves site files through its own host, so the bucket never needs public read.
  2. Create an access key scoped to that bucket and keep both halves to hand.
  3. Copy the bucket’s S3 API endpoint. It has to be an https address.
  4. Paste the endpoint, bucket, and key into the form. Wirecopy saves the connection with encrypted keys, then tests it. Only a verified connection can be used for publishing.

Grant the connection these bucket-scoped permissions:

s3:PutObject s3:GetObject s3:DeleteObject s3:ListBucket

Access keys are encrypted at rest. Before a bucket is marked usable, Wirecopy writes, reads back, and deletes a probe object; site files are checked against the publish manifest before they are served.

Your storage provider bills you separately for storage and requests. Connected sites count toward Wirecopy’s plan limits. Keep the bucket private and reachable over HTTPS while a site is active.

Manage what you’ve shared

Open the dashboard, choose a file or drop one in, and publish. Manage active links and sites, revoke early, and create device tokens for CLI and agents under Apps & CLI.

Free includes five publishes a day. Compare plans when you need higher limits or your own bucket.

HTTP API

POST /api/v1/upload_intents
Authorization: Bearer wc_live_…
Content-Type: application/json

{"upload":{"filename":"report.pdf","content_type":"application/pdf","byte_size":482091}}

PUT the exact bytes to the returned upload.url, including its returned headers. Then call POST /api/v1/upload_intents/:id/complete.

File upload lifecycle

created→uploading→quarantined→available

Terminal alternatives are rejected, expired, revoked, and deleted. Links expire on their own. Revoke anytime from the dashboard or CLI. A site has its own publishing and retirement flow; the states above describe ordinary file uploads.

Expiry and revocation stop new access through the shared link. Already issued download URLs can work for up to five minutes, and saved copies remain with their recipients. See the security and access details.