[GH-ISSUE #2362] Integrate SingleFile CLI for server-side archiving? #1430

New issue

Open

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

kerem commented

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

Owner

Originally created by @foxdodo on GitHub (Jan 8, 2026).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2362

Describe the feature you'd like

I'm currently self-hosting this using Docker.

I know the standard workflow is to use the SingleFile extension on the client side and push the data to Karakeep via API. However, I often run into issues when doing this on iOS Safari. Specifically, when archiving sites like X.com (Twitter) or Discourse forums, the long reply threads often get cut off or don't capture completely. (The desktop extension works fine, but mobile is a bit flaky).

I recently tried another project, linkding, which offers a Docker image integrated with SingleFile CLI. I found that their server-side scraping is much more reliable than capturing via the iOS browser.

I was wondering if it would be possible to integrate SingleFile CLI here to replace (or strictly as an option for) the current default server-side scraping method?

Thanks!

Describe the benefits this would bring to existing Karakeep users

Improved reliability for mobile users: Currently, capturing complex SPAs (Single Page Applications) like X.com or Discourse on mobile devices (especially iOS Safari) is unstable due to browser limitations. Server-side integration would ensure these pages are captured completely every time.

Consistent archive quality: By offloading the rendering and capturing process to the server (via SingleFile CLI), the archive quality becomes independent of the client device's performance or browser restrictions.

Better workflow: Users can simply trigger the save action from their phone without having to keep the browser tab open and wait for the extension to finish processing heavy pages.

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

Yes, but with limitations.

Currently, the goal is achieved by using the SingleFile browser extension on the client side. While this works perfectly on desktop browsers, it is often flaky on mobile browsers (iOS Safari) due to strict resource limits and WebKit behaviors.

The requested server-side approach acts as a robust fallback or alternative for scenarios where the client-side extension fails to capture the full content (e.g., long threads or dynamic comments).

Have you searched for an existing open/closed issue?

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

Additional context

No response

Originally created by @foxdodo on GitHub (Jan 8, 2026). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2362 ### Describe the feature you'd like I'm currently self-hosting this using Docker. I know the standard workflow is to use the SingleFile extension on the client side and push the data to Karakeep via API. However, I often run into issues when doing this on iOS Safari. Specifically, when archiving sites like X.com (Twitter) or Discourse forums, the long reply threads often get cut off or don't capture completely. (The desktop extension works fine, but mobile is a bit flaky). I recently tried another project, [linkding](https://www.google.com/url?sa=E&q=https%3A%2F%2Fgithub.com%2Fsissbruecker%2Flinkding), which offers a Docker image integrated with SingleFile CLI. I found that their server-side scraping is much more reliable than capturing via the iOS browser. I was wondering if it would be possible to integrate SingleFile CLI here to replace (or strictly as an option for) the current default server-side scraping method? Thanks! ### Describe the benefits this would bring to existing Karakeep users Improved reliability for mobile users: Currently, capturing complex SPAs (Single Page Applications) like X.com or Discourse on mobile devices (especially iOS Safari) is unstable due to browser limitations. Server-side integration would ensure these pages are captured completely every time. Consistent archive quality: By offloading the rendering and capturing process to the server (via SingleFile CLI), the archive quality becomes independent of the client device's performance or browser restrictions. Better workflow: Users can simply trigger the save action from their phone without having to keep the browser tab open and wait for the extension to finish processing heavy pages. ### Can the goal of this request already be achieved via other means? Yes, but with limitations. Currently, the goal is achieved by using the SingleFile browser extension on the client side. While this works perfectly on desktop browsers, it is often flaky on mobile browsers (iOS Safari) due to strict resource limits and WebKit behaviors. The requested server-side approach acts as a robust fallback or alternative for scenarios where the client-side extension fails to capture the full content (e.g., long threads or dynamic comments). ### Have you searched for an existing open/closed issue? - [x] I have searched for existing issues and none cover my fundamental request ### Additional context _No response_

kerem added the

feature request

status/untriaged

labels

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

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#1430

No description provided.

Rows
Columns