karakeep-app/karakeep

Allow setting max filesize for archived webpages

Open

#1,687 opened on Jun 29, 2025

View on GitHub
 (1 comment) (1 reaction) (0 assignees)TypeScript (1,356 forks)auto 404
feature requestgood first issuepri/lowstatus/approved

Repository metrics

Stars
 (27,587 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the feature you'd like

Please add a config value/environment variable to enforce a max filesize for archived webpages. If this size is exceeded, Karakeep should discard the webpage.

Describe the benefits this would bring to existing Karakeep users

Some large or media rich websites will create extremely large archive files, some 1GB+: https://github.com/karakeep-app/karakeep/issues/770 This takes up significant storage and doesn't end up rendering in browsers anyways, it just causes hangs/crashes when opened.

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

Not automatically, you would have to manually purge all assets above a certain filesize in settings.

Have you searched for an existing open/closed issue?

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

Additional context

https://github.com/karakeep-app/karakeep/issues/770

Contributor guide

Research direction
Implement a new configuration option (environment variable or config file) to set a maximum file size for archived webpages. When archiving a webpage, after downloading the assets, check the total size and if it exceeds the limit, discard the archive. Look for existing archiving logic and configuration patterns in the codebase.
Tech stack
typescript
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75