Clipcroft vs cl1p.net

cl1p.net is one of the oldest internet clipboards on the web — a charming, minimal "type a URL, paste data, retrieve elsewhere" tool that's been around for over a decade. Clipcroft is a different shape of online clipboard: real-time multi-device sync, file transfers, persistent history, and optional end-to-end encryption — built for ongoing use across your own devices rather than one-off paste-by-URL.

Feature comparison

Note: third-party feature details change. The summary above reflects what was publicly documented at the time of writing.

Where cl1p.net wins

• The custom-URL pattern is iconic. Anything you type after cl1p.net/ becomes a clipboard. cl1p.net/projectalpha just works. It's a UX detail Clipcroft doesn't try to copy — Clipcroft uses short numeric IDs by design (and longer alphanumeric IDs are on the roadmap).
• HTTP API for scripts. cl1p documents a small HTTP API so you can pipe shell output into a clipboard from a CI job or a curl one-liner. Clipcroft is currently browser-only with no public API; this is the main practical advantage cl1p has for scripting workflows.
• Brand and minimalism. cl1p has been online for many years, the front page is one input field, and "destroyed on read" is the kind of zero-config-ephemeral semantics some users prefer for one-off shares.

Where Clipcroft wins

• Real-time live sync, not one-shot pull. cl1p.net's model is "paste here, fetch from there" — the second device only sees what was on the URL the moment it opened it, and once read, the entry is gone. Clipcroft keeps every connected device updated continuously: paste text on one device and it appears on every other connected device instantly.
• Files and folders, not just text. Clipcroft handles files of any size (no per-file cap), folder drops with their full directory structure preserved, and image paste with auto-naming for screenshots. cl1p.net is centred on text and short data.
• Persistent clipboard history with bulk export. Clipcroft keeps thousands of items per clipboard, automatically organised into Texts, URLs, Files, and Images sections, with bulk operations per category (download all, share all, ZIP all, export URLs as HTML). cl1p destroys entries on read by default.
• Multi-device live fan-out. Up to 20 devices on the same clipboard; one drop reaches all of them via parallel WebRTC pipes from a single sender. cl1p is pairwise — one paste, one fetcher, gone.
• Optional end-to-end encryption with idle auto-lock. Set a clipboard-level password and Clipcroft encrypts contents in the browser before they leave the device, including the localStorage at rest. AutoForget drops the in-memory key after a configurable idle window so a stepped-away device can't be raided. cl1p does not document end-to-end encryption.
• Multiple clipboards per device. One browser holds many independent clipboards (work, personal, family, project), each with its own history, password, retention, and device list. No account required. cl1p is one URL per clipboard with no concept of "your clipboards".
• Multi-file upload queue with retry, cancel, and resume. Drop any number of files; each one tracks its own state (Queued, Preparing, Connecting, Transferring, Retrying, Completed, Failed, Canceled). Cancel one without disturbing the rest. Auto-resume from the last received byte if the network drops. cl1p has none of this.
• Configurable retention. Items live in your browser for 3 days by default, configurable in Settings up to 30 days or down to nothing. cl1p's default is "destroyed on first read"; the optional retention is up to one month.

Use-case recommendations

Use cl1p.net when: you want a memorable short URL for a one-off text paste, you don't care about history or multi-device sync, and the data should disappear the moment someone opens it. Or: you want a small HTTP API to pipe output from a script.

Use Clipcroft when: you want a real online clipboard that's continuously synced across all your devices, with files, folders, history, optional encryption, and a password-protected option that auto-locks when you walk away.

Frequently asked questions

What is cl1p.net?

cl1p.net is one of the oldest internet clipboards. The user picks any URL beginning with cl1p.net (for example cl1p.net/myclipboard), pastes data into it, and on another device opens the same URL to retrieve it. By default the entry is destroyed when first read; an optional retention up to one month is available.

Does cl1p.net support real-time sync?

No. cl1p.net is a one-shot pull model — you paste into a URL and someone else fetches that URL. There is no live sync between connected devices. Clipcroft is real-time: text and files appear on every connected device the moment they're added.

Does cl1p.net support files?

cl1p.net is centred on text and short data. There is no first-class file-transfer flow with progress, resume, or queue. Clipcroft handles text, URLs, files, folders, and images, with a multi-file upload queue and auto-resume on disconnect.

Is cl1p.net encrypted?

cl1p.net does not document end-to-end encryption. The transport layer uses HTTPS, but contents are visible to the server. Clipcroft offers optional per-clipboard end-to-end encryption — when a password is set, contents are encrypted in the browser before they leave the device, and the server never sees plaintext.

Which one should I use?

Use cl1p.net for a quick one-off paste-by-URL where you want a memorable short address (cl1p.net/anything) and the data lives only as long as the recipient takes to open it. Use Clipcroft for ongoing real-time sync between your own devices, file transfers, multiple clipboards, persistent history, and optional encryption with idle auto-lock.

Is there a Clipcroft alternative to cl1p.net's API?

Not yet. cl1p.net documents a small HTTP API for programmatic access. Clipcroft is currently a browser-only product without a public API; that's the main practical advantage cl1p has for scripting use cases.