How to Organize Bookmarks in Raindrop.io for a Website Project

On this page

1. Choose three references and a simple structure #

Open Raindrop.io and sign in to its web app. This example uses a parent collection called Website research, with Accessibility and CSS underneath it. Those names describe work you'll return to, instead of an unexplained collection called Interesting.

Use these three references:

• MDN accessibility documentation, tagged reference and accessibility.
• W3C accessible forms tutorial, tagged reference and forms.
• MDN CSS grid documentation, tagged reference and layout.

The collection says which project owns the reference. A tag says what you'll want to find across projects later. You should finish with three links whose purpose is obvious without reopening all three pages.

2. Create the parent and nested collections #

In the sidebar, click the plus icon, type Website research and press Enter. The collection should appear in the sidebar. Raindrop's collection documentation describes this web and desktop route.

Right-click the new collection and choose Create nested collection. Name the child Accessibility. Repeat to add CSS. The sidebar should show both children beneath Website research, with an arrow to expand or collapse the parent.

If you created a separate collection by mistake, drag it onto the intended parent to nest it. Dragging it back into empty sidebar space removes the nesting. That gives you a way to correct the structure without deleting the saved material.

Keep the example small. You can add another collection once the work needs it; making twenty empty destinations makes the next save harder to place.

3. Save the references into their collections #

Open Accessibility, choose + Add in the toolbar, paste the MDN accessibility URL and choose Save. Repeat for the W3C forms tutorial. Open CSS and save the grid page there.

You should see two bookmarks in Accessibility and one in CSS. Raindrop's bookmark instructions also describe saving through its browser extension: open the Raindrop icon, choose a collection, add optional tags and choose Save.

Use the extension route for a page you're already reading. Use + Add when you have a URL to place directly in a known collection. Both routes should leave the reference in the collection you chose.

Check the destination before closing the save form. A page saved without a collection goes to Unsorted, the built-in inbox. That's fine for quick capture, but it still needs sorting before the project library is finished.

4. Organize bookmarks with titles and tags #

Right-click a bookmark and choose Edit. Check its title and description, then enter the example tags in the Tags field. Raindrop's tag instructions say to separate multiple tags with commas.

Use reference, forms for the W3C tutorial. The title should explain the page, such as Accessible forms: labels and instructions. A descriptive title helps when a project's references include several pages from the same documentation site.

For several bookmarks, select their checkboxes and use Add tags in the top toolbar. Apply reference to all three, then keep the subject tags specific. You should be able to find the forms tutorial by its name or subject without remembering which browser tab it originally came from.

I'd avoid tags that mean almost the same thing. Pick forms or form-design for this collection and use it consistently. A tidy vocabulary is easier to maintain than a long list of slight variations.

5. Move an unsorted link into the project #

If you saved a reference into Unsorted, drag it onto the intended collection in the sidebar. For several items, select them and choose Move, then select the destination. The collection documentation describes both routes.

For this example, place the accessibility overview and forms tutorial in Accessibility, with the grid reference in CSS. Check that the destination now contains the intended items. Moving a bookmark changes its collection while its tags continue to describe the subject.

Every bookmark belongs to one collection. Use tags when the same reference applies to several areas; saving another copy just to make it appear elsewhere adds cleanup work. If you prefer writing your own analysis beside references, the offline note-taking shortlist covers that approach.

6. Export a backup and inspect it #

Open Settings, then Backups, and choose Create new. Raindrop's backup instructions say to wait for an email notification, then download from the same page. Choose HTML for a portable bookmark file.

Open the downloaded HTML locally in a browser. Look for all three example URLs and the project collection names. This checks that you downloaded the file you intended; it doesn't require importing copies back into the account.

For a single collection, open it and choose Export. Use the whole-account backup when the wider collection structure matters. If you've uploaded PDFs or images, download those separately through All bookmarks → Export → ZIP; they aren't included as file contents in the bookmark backup.

Store the downloaded file somewhere you can find later. The Joplin backup guide covers a separate recovery routine for written notes. Links and notes can support the same project while needing different backup files.

7. Check an import before moving a large old library #

If you're bringing browser bookmarks into Raindrop, open the Import page, upload the exported file and review the summary. It shows the bookmarks, folders, tags and highlights found. Choose Start import only after those figures look reasonable, and keep the tab open until upload finishes.

Begin with a small representative collection containing a nested folder and a few tags. After import, inspect the names and nesting. Raindrop's import documentation says duplicates are skipped and existing bookmarks aren't overwritten. Reimporting a revised file won't automatically update every existing item.

For this three-link example, an import isn't necessary if you've already added the references. Keep it as the next route for an older library. A successful sample is more informative than reorganizing thousands of links after one unchecked upload.

Known problems and fixes #

A manual backup appears to do nothing

In a March 7, 2026 discussion, a user repeatedly chose Create new because the backup page didn't clearly show progress. The reply advised allowing a few minutes for the notification email. Follow that notification, then return to Backups to download; repeated clicks don't make the generation finish sooner.

Imported folders arrive flattened

A February 3, 2026 follow-up reported different results from a structured JSON file and a plain-text URL list: the text import flattened the folders. Use a structured bookmark export when organization matters and inspect the import summary. If a small collection arrives flat, rebuild its nesting by dragging collections under the parent before importing the rest.

A working intranet page is marked broken

For Pro's broken-link feature, the official help documents Settings → App → Broken links modes. Basic checks explicit missing-page responses; Off disables detection. Use the less strict mode for local or intranet links that the service can't reach normally, then allow a few hours for results to update.

Troubleshooting #

Variations for another research habit #

Keep a reading queue separate from reference material

Create a Read next collection for articles you intend to read soon. Put durable project references in the project collections. If reading is the main job, Instapaper offers a dedicated reading approach.

Review new posts before bookmarking the best ones

Use an RSS reader to follow sources and save only the articles you expect to revisit. The Inoreader guide explains that feed-review routine. This keeps your reference library from filling with every post a source publishes.

Keep analysis in a separate note

Link a reference from your own research note and write why it mattered. A bookmark description helps retrieval, while a longer note can connect several sources into a decision. Obsidian vs Joplin compares two ways to organize that writing.

Completion checklist #

• Website research contains Accessibility and CSS as nested collections.
• All three example references open the expected pages.
• Titles explain what the saved pages contain.
• Tags use a small consistent vocabulary.
• Unsorted contains no unfinished items from the example.
• The downloaded HTML backup contains the intended links.
• Uploaded files, if any, have their separate export.
• A sample import was inspected before any large migration.

Next steps #

Consider Linkwarden when preserved page content and server control become the priority, or linkding for a smaller self-hosted library. Keep the collection focused on references you can explain and find again.

Related reading #

Best Free Bookmark Managers for Links You Want to Find Again, Raindrop.io vs Linkwarden: Easy Capture or Your Own Archive?, Tool details, Other options.