Raindrop.io vs Pinboard: Visual Collections or Minimal Archive?

Raindrop.io and Pinboard both save URLs, but they impose very different habits. Raindrop is a visual, multi-device library built around collections. Pinboard is a compact, tag-first database whose appeal is speed, privacy, feeds, and automation. The useful question is not which has more features; it is whether you want to curate a library or query a ledger.

The short answer

• Choose Raindrop.io for nested folders, thumbnails, first-party apps, file uploads, highlights, and shared collections.
• Choose Pinboard for a low-distraction chronological list, tag-based retrieval, RSS/API workflows, and an explicitly tracker-free service.
• Pay for archiving only after defining “archive.” Both paid offerings preserve page content and add full-text search, but neither export should be assumed to include a portable copy of every archived page.

Current plans and the real cost

Raindrop.io	Pinboard
Entry plan	Free indefinitely	$22/year
Archive/full-text tier	Pro; price varies by billing route and region	$39/year archival account
Free-plan scale	Unlimited bookmarks, collections, highlights, and devices	No free tier
Paid extras	Permanent copies, full-text search, AI tools, reminders, annotations, daily backups, 10 GB/month uploads	Saved page copies, full-text search, dead-link checks

Raindrop's official pricing page currently lists the plan contents and shows local checkout pricing; Pinboard's home page lists $22/year and describes archiving as a higher-priced option. Prices and plan contents were checked on 21 September 2026. Check checkout before buying, particularly for taxes, app-store billing, or currency conversion.

Raindrop's free tier is not a token trial: it includes import/export, collaboration, official apps, and unlimited core objects. Paying makes sense when the saved page—not merely its URL—must remain searchable after the source changes. Pinboard has no free account, so its value proposition starts with a paid, deliberately spare service and no advertising or trackers.

Organization: hierarchy versus vocabulary

Raindrop gives each item a home in a collection, supports nested collections, and adds tags. Grid, masonry, headline, and list-style browsing make covers and file types useful retrieval cues. This suits project libraries, design references, shopping research, and any collection people recognize visually. Shared collections also make it the stronger choice when another person must browse or add links.

Pinboard treats tags as the primary structure. “Bundles” group related tags; they are not a nested folder tree. That is powerful if you prefer intersections such as research + databases and do not want to decide one canonical folder. Its dense reverse-chronological list also rewards quick capture with a title, description, private/public state, and “to read” flag. See Pinboard's explanations of tags, bundles, privacy lock, and read-later shortcuts.

The switching implication is important: Raindrop collections map reasonably well to browser folders, while a mature Pinboard tag vocabulary does not become a clean folder tree automatically. Conversely, exporting Raindrop to a tag-only tool can flatten useful nesting.

Capture, apps, and collaboration

Raindrop publishes apps for Mac, iOS, and Android plus extensions for Chrome, Safari, Firefox, and Edge. Its first-party experience is consistent across the web and devices. It can save tabs, highlight pages, upload files, and share or collaboratively edit collections.

Pinboard's own workflow is web-first: bookmarklets, a mobile site, save-by-email, feeds, and a Delicious-compatible API. Third-party clients fill the native-app gap. That is an advantage for people who already have scripts or a favorite independent client, but a disadvantage for anyone who expects the vendor to own the whole mobile experience. Pinboard can publish individual bookmarks and public tag feeds, yet it is not a shared workspace comparable to Raindrop collections.

Search, reading, and preservation

On Raindrop Free, search is primarily about bookmark metadata. Pro extends it to page content and permanent copies; the vendor says full-text search can include PDFs and YouTube speech. Pro also detects duplicate and broken links. Raindrop has a preview/reader experience and highlights, but it remains a bookmark manager rather than a reading queue with reading progress.

Pinboard's base account searches bookmark fields and tags. Its archival account fetches a copy, indexes the full text, and checks dead links. The separate “unread” flag and oldest/random-unread views are lightweight triage, not an Instapaper-style offline reading environment. Dynamic, authenticated, paywalled, or script-heavy pages may not archive perfectly in either service; keeping a legal local PDF is safer for irreplaceable research.

Privacy and ownership

Pinboard describes itself as independently run, with no ads and no trackers, and supports private-by-default bookmarks plus a privacy lock. It is still hosted software: privacy from advertising does not mean self-hosting or end-to-end encryption.

Raindrop is also managed cloud software. Its richer previews, indexing, integrations, AI features, and collaboration necessarily involve more server-side processing than a bare URL list. Consult Raindrop's privacy policy if saved URLs themselves are sensitive. Neither product is the right repository for secrets, confidential client URLs, or credentials.

Portability and switching costs

Raindrop exports the whole account or selected collections as HTML, CSV, or TXT. Its export documentation says account backups include bookmarks, collections, tags, highlights, and notes, while uploaded files require a separate ZIP export. Pro keeps up to 30 automatic daily backups and can send backups to supported cloud drives. Its importer accepts HTML, CSV, JSON, TXT, and ENEX; Pinboard JSON is the most complete Pinboard-to-Raindrop route.

Pinboard exports XML, JSON, or Netscape bookmark HTML and also exposes the API, according to its official export guide. Use HTML for widest compatibility and JSON when the destination explicitly understands Pinboard metadata. Before cancelling either service:

1. Export a small sample and inspect titles, URLs, tags, descriptions/notes, timestamps, privacy state, and unread state.
2. Export uploaded files separately from Raindrop.
3. Assume shared permissions, visual covers, collection nesting, bundles, and archived page copies need separate verification.
4. Import the sample into the destination before moving the full library; duplicate handling differs.

Who should avoid each product?

Avoid Raindrop if you dislike visual metadata, want every interaction scriptable through a minimal long-established API, or require self-hosting. Avoid Pinboard if you need first-party native apps, nested collections, collaborative editing, rich previews, PDF uploads, or a free tier. Also avoid both as your only evidence archive when retention and export of preserved files must be independently auditable.

Where Save This One fits

Save This One is relevant when the job is narrower: save mixed links, add tags and notes, search later, and connect through browser/mobile capture, an API, or MCP. It avoids Raindrop's collection system and Pinboard's paid entry point. It does not replace Raindrop's visual library and collaboration or Pinboard's paid archival crawl. If permanent snapshots, nested collections, or a mature ecosystem of Pinboard clients are requirements, choose the product that actually supplies them.

Moving from Raindrop? Follow the Raindrop migration guide. From Pinboard, start with Netscape HTML for broad compatibility and retain a JSON export as a richer backup.