mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #266] Allow saving screenshots as JPG #3209
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#3209
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dzek69 on GitHub (Sep 12, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/266
Type
What is the problem that your feature request solves
I would like to save page screenshots as JPG to save space. PNG's of websites that are mostly images are using more disk space that I'd like them to. Allowing saving screenshot as JPG would solve that.
Describe the ideal specific solution you'd want, and whether it fits into any broader scope of
Ideally I should be able to select jpeg quality as well. Having default
How badly do you want this new feature?
@pirate commented on GitHub (Sep 19, 2019):
Unfortunately this is not supported by chrome, so it would have to be a separate program that runs after the screenshot process to convert the PNGs to JPGs. I'll leave this open to see if other people want this too, but I cant promise this feature will be added anytime soon.
As a quick fix in the meantime, might I suggest storing the entire archive dir on a compressed filesystem like ZFS?
@LaserWires commented on GitHub (Sep 19, 2019):
It would be more ideal to employ image base64 format and imbed them directly without populating the archive directory.
@dzek69 commented on GitHub (Sep 19, 2019):
@LaserWires why it would be more ideal?
I disagree, because it's easier to do something with it if it's stored as a file instead of embedded into something else. Additionally encoding something into base64 makes it's around 37% bigger. Huge waste of space. I see no advantages.
@dzek69 commented on GitHub (Sep 19, 2019):
@pirate thank you for your reply. I think I'm gonna do some post-processing then, to replace png with jpg
If you feel like implementing it with external tools someday - please leave this ticket open, if not - feel free to close.
@pirate commented on GitHub (Sep 20, 2019):
I think I'm going to close this for now, and keep compressed filesystems as the recommended solution for disk space saving. Images are only a small potential source of bloat, and LZ4 compression on the whole folder will do a better overall job than any individual fix.