[GH-ISSUE #2443] Add bibtex-like citation keys #1471

New issue

Open

opened 2026-03-02 11:57:33 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 11:57:33 +03:00

Owner

Originally created by @phista on GitHub (Feb 1, 2026).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2443

Describe the feature you'd like

I would like to request to add bibtex-like citation keys for each saved page so I can utilize karakeep to maintain a copy of the webpages that I cite in academic works.

For example, the page Example FT Article would have a unique key, such as ft.com20260202.

As an extension of this feature, exporting these pages as bibtex should be relatively straight forward given the available information:

@online{ft.com20260202,
  author = {ft.com},
  title = {China’s genius plan to win the AI race is already paying off},
  year = 2026,
  url = {https://www.ft.com/content/68f60392-88bf-419c-96c7-c3d580ec9d97},
  urldate = {2026-02-02}
}

Describe the benefits this would bring to existing Karakeep users

When working with webpages in an academic context (when citing them as sources), it is important to take note when a page was accessed, and make sure the content is archived for later reference. This is the core problem karakeep solves. I would like to have a short, human comprehensible key string that I can use to refer to a specific version of a saved webpage when writing papers. A simple user-definable string as permanent identifier should be sufficient, as citation management can be done in specialized programs (e.g. Zotero, Citavi), but there is currently no way to cross-reference between citation database and a webpage storage tool. Bibtex export would be a bonus.

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

Have you searched for an existing open/closed issue?

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

Additional context

I think that only selected pages need a key like this, not all of them. Also I think it is not necessary to create the string automatically, it would be sufficient to store a user-defined string, ensure uniqueness, and make them searchable.

I appreciate your work, thank you!

Originally created by @phista on GitHub (Feb 1, 2026). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2443 ### Describe the feature you'd like I would like to request to add bibtex-like citation keys for each saved page so I can utilize karakeep to maintain a copy of the webpages that I cite in academic works. For example, the page [Example FT Article](https://www.ft.com/content/68f60392-88bf-419c-96c7-c3d580ec9d97) would have a unique key, such as `ft.com20260202`. As an extension of this feature, exporting these pages as bibtex should be relatively straight forward given the available information: ``` @online{ft.com20260202, author = {ft.com}, title = {China’s genius plan to win the AI race is already paying off}, year = 2026, url = {https://www.ft.com/content/68f60392-88bf-419c-96c7-c3d580ec9d97}, urldate = {2026-02-02} } ``` ### Describe the benefits this would bring to existing Karakeep users When working with webpages in an academic context (when citing them as sources), it is important to take note when a page was accessed, and make sure the content is archived for later reference. This is the core problem karakeep solves. I would like to have a short, human comprehensible key string that I can use to refer to a specific version of a saved webpage when writing papers. A simple user-definable string as permanent identifier should be sufficient, as citation management can be done in specialized programs (e.g. Zotero, Citavi), but there is currently no way to cross-reference between citation database and a webpage storage tool. Bibtex export would be a bonus. ### Can the goal of this request already be achieved via other means? No ### Have you searched for an existing open/closed issue? - [x] I have searched for existing issues and none cover my fundamental request ### Additional context I think that only selected pages need a key like this, not all of them. Also I think it is not necessary to create the string automatically, it would be sufficient to store a user-defined string, ensure uniqueness, and make them searchable. I appreciate your work, thank you!