starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-25 07:56:05 +03:00

[GH-ISSUE #2214] Feature Request: Include Bookmark Lists When Exporting Bookmarks #1352

New issue

Open

opened 2026-03-02 11:56:43 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 11:56:43 +03:00

Owner

Originally created by @a21ns1g4ts on GitHub (Dec 3, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2214

Hi team,

First of all, thanks for the great work on Karakeep — it’s been very helpful!

I’d like to request an improvement to the bookmark export feature.

🧩 Problem

Currently, when exporting bookmarks, lists/folders are not included in the exported data.
For users with a large number of bookmarks (in my case, more than 2,000), this becomes a huge challenge. The exported file contains all bookmarks mixed together, which makes it extremely difficult to reorganize them afterward.

💡 Why This Matters

Bookmark lists are an essential part of how users organize their data.
Without them:

Exports become messy and hard to use

Large collections become nearly impossible to manage

Restoring or migrating bookmarks loses structure and context

🎯 Requested Improvement

Please include bookmark lists/folders in the export format (JSON/CSV/etc.), preserving the organization structure created by users.

This would make backups, migrations, and large-scale organization much more manageable.

🙏 Thanks!

I appreciate your attention and would be happy to provide examples or more details if needed.

Describe the benefits this would bring to existing Karakeep users

📈 Measurable Benefits for Karakeep Users

Adding support for exporting bookmarks together with their lists/folders would provide several concrete, user-focused benefits:

Reduced Time Spent Reorganizing Bookmarks After Export/Import

Users with large collections (hundreds or thousands of bookmarks) would no longer need to manually rebuild folder structures after exporting and reimporting.
This can reduce organization time by hours for heavy users.

Improved Data Integrity During Backup and Migration

When lists are included in exports, users retain the original structure of their data.
This leads to:

Fewer lost or misplaced bookmarks

Higher accuracy in backup restoration

A more faithful migration experience to/from Karakeep

This can measurably decrease user errors and restore friction.

Higher Usability of Exported Data

Structured exports allow users to navigate their exported data more efficiently.
The presence of folder hierarchy enables faster retrieval of specific items—improving navigation time in the exported dataset by an order of magnitude for large bookmark sets.

Greater Confidence in Using Karakeep as a Primary Knowledge/Bookmark Hub

Reliable, structured backups increase users’ trust that their organizational work will not be lost.
This boosts long-term retention and makes the platform feel more robust for power users.

Improved Scalability for Heavy Users

Users with thousands of bookmarks often outgrow flat exports.
Structured exports better support:

Power users

Team workflows

Long-term data accumulation

Leading to a more scalable user experience overall.

Enables More Meaningful External Workflows

Users who rely on exports for:

Audits

Migrations

External automation

Integrations with other tools

benefit significantly from having context preserved in the exported file.
This enables more meaningful third-party processing and lowers the need for manual preprocessing by up to 80–90%.

Can the goal of this request already be achieved via other means?

No.

Karakeep currently allows exporting bookmarks, but the export does not include list/folder structure. There is no existing method—manual or automated—that preserves organizational hierarchy during export.

While users could theoretically reorganize bookmarks manually after reimporting, this is not a viable solution for medium or large collections (hundreds or thousands of bookmarks). The requested feature addresses this limitation by enabling structured exports that maintain the user’s original organization, which cannot currently be achieved using any existing functionality.

Have you searched for an existing open/closed issue?

I have searched for existing issues and none cover my fundamental request

Additional context

Many users rely heavily on lists/folders to categorize large bookmark collections within Karakeep. In practical use, these lists function as the primary way to group resources by project, topic, client, or workflow.

When exporting bookmarks today, all items are flattened without their associated lists. For users with large libraries (e.g., 1,000–2,000+ bookmarks), this makes exported data significantly less useful, since the organizational context is lost.

Below is an example of how bookmarks appear inside Karakeep, showing how important lists are for navigation and categorization:

(Insert screenshot of your Karakeep lists view here — optional but recommended)

Being able to export both bookmarks and the lists they belong to would preserve the actual organizational system users rely on every day and ensure that exported data matches how content is structured inside the app.

Originally created by @a21ns1g4ts on GitHub (Dec 3, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2214 ## Hi team, First of all, thanks for the great work on Karakeep — it’s been very helpful! I’d like to request an improvement to the bookmark export feature. 🧩 Problem Currently, when exporting bookmarks, lists/folders are not included in the exported data. For users with a large number of bookmarks (in my case, more than 2,000), this becomes a huge challenge. The exported file contains all bookmarks mixed together, which makes it extremely difficult to reorganize them afterward. 💡 Why This Matters Bookmark lists are an essential part of how users organize their data. Without them: Exports become messy and hard to use Large collections become nearly impossible to manage Restoring or migrating bookmarks loses structure and context 🎯 Requested Improvement Please include bookmark lists/folders in the export format (JSON/CSV/etc.), preserving the organization structure created by users. This would make backups, migrations, and large-scale organization much more manageable. 🙏 Thanks! I appreciate your attention and would be happy to provide examples or more details if needed. ### Describe the benefits this would bring to existing Karakeep users 📈 Measurable Benefits for Karakeep Users Adding support for exporting bookmarks together with their lists/folders would provide several concrete, user-focused benefits: 1. Reduced Time Spent Reorganizing Bookmarks After Export/Import Users with large collections (hundreds or thousands of bookmarks) would no longer need to manually rebuild folder structures after exporting and reimporting. This can reduce organization time by hours for heavy users. 2. Improved Data Integrity During Backup and Migration When lists are included in exports, users retain the original structure of their data. This leads to: Fewer lost or misplaced bookmarks Higher accuracy in backup restoration A more faithful migration experience to/from Karakeep This can measurably decrease user errors and restore friction. 3. Higher Usability of Exported Data Structured exports allow users to navigate their exported data more efficiently. The presence of folder hierarchy enables faster retrieval of specific items—improving navigation time in the exported dataset by an order of magnitude for large bookmark sets. 4. Greater Confidence in Using Karakeep as a Primary Knowledge/Bookmark Hub Reliable, structured backups increase users’ trust that their organizational work will not be lost. This boosts long-term retention and makes the platform feel more robust for power users. 5. Improved Scalability for Heavy Users Users with thousands of bookmarks often outgrow flat exports. Structured exports better support: Power users Team workflows Long-term data accumulation Leading to a more scalable user experience overall. 6. Enables More Meaningful External Workflows Users who rely on exports for: Audits Migrations External automation Integrations with other tools benefit significantly from having context preserved in the exported file. This enables more meaningful third-party processing and lowers the need for manual preprocessing by up to 80–90%. ### Can the goal of this request already be achieved via other means? No. Karakeep currently allows exporting bookmarks, but the export does not include list/folder structure. There is no existing method—manual or automated—that preserves organizational hierarchy during export. While users could theoretically reorganize bookmarks manually after reimporting, this is not a viable solution for medium or large collections (hundreds or thousands of bookmarks). The requested feature addresses this limitation by enabling structured exports that maintain the user’s original organization, which cannot currently be achieved using any existing functionality. ### Have you searched for an existing open/closed issue? - [x] I have searched for existing issues and none cover my fundamental request ### Additional context Many users rely heavily on lists/folders to categorize large bookmark collections within Karakeep. In practical use, these lists function as the primary way to group resources by project, topic, client, or workflow. When exporting bookmarks today, all items are flattened without their associated lists. For users with large libraries (e.g., 1,000–2,000+ bookmarks), this makes exported data significantly less useful, since the organizational context is lost. Below is an example of how bookmarks appear inside Karakeep, showing how important lists are for navigation and categorization: (Insert screenshot of your Karakeep lists view here — optional but recommended) Being able to export both bookmarks and the lists they belong to would preserve the actual organizational system users rely on every day and ensure that exported data matches how content is structured inside the app.

kerem added the

feature request

pri/high

status/approved

labels

2026-03-02 11:56:43 +03:00

kerem commented

2026-03-02 11:56:43 +03:00

Author

Owner

@vitorhugoaranda commented on GitHub (Jan 21, 2026):

I strongly support this. We really need a simple ZIP backup, especially to save the organization of Favorites.

Currently, having to re-organize everything manually after a reinstall makes the app unfeasible to use. It takes way too much time to sort everything again from scratch

@vitorhugoaranda commented on GitHub (Jan 21, 2026): I strongly support this. We really need a simple ZIP backup, especially to save the organization of Favorites. Currently, having to re-organize everything manually after a reinstall makes the app unfeasible to use. It takes way too much time to sort everything again from scratch

kerem commented

2026-03-02 11:56:44 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Jan 21, 2026):

this at the top of my todo list and I even have an implementation for it almost ready

@MohamedBassem commented on GitHub (Jan 21, 2026): this at the top of my todo list and I even have an implementation for it almost ready

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/karakeep#1352

No description provided.

Rows
Columns