mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-15 19:06:40 +03:00
Bookstack Image Resolution #2148
Reference in New Issue
Block a user
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 @TurieE90 on GitHub (Mar 9, 2021).
Hi,
I am new to Github thanks to this issue I'm having with Bookstack. I have been uploading documentation and manuals to Bookstack for my organization and am finding that images are scaled down when I upload them.
I upload screenshots and images using the "insert an image" function, but they still come out blurry on the site and also when I export to PDF.
I will be very grateful if someone could help me with resolving this issue.
Thanks so much for your help in advance
@ssddanbrown commented on GitHub (Mar 10, 2021):
Hi @TurieE90,
Images uploaded to BookStack should be auto-scaled to 1680px wide, which is 2x the default image display view which should ideally not be blurry. Also, if using the default WYSIWYG editor to insert images, you should be able to click through on the image to view the original.
If you have a genuine example of an image where it becomes blurry after upload it would help to provide that if possible.
@TurieE90 commented on GitHub (Mar 15, 2021):
Hi @ssddanbrown,
Thanks for responding! I have attached an image for example.
@ssddanbrown commented on GitHub (Apr 19, 2021):
Hi @TurieE90,
Sorry for my late response.
When uploading the provided image to BookStack I can't really see any difference in the uploaded result to be honest.
If you see that become blurry after upload, Would you be able to download and share the copy after upload to BookStack? Just so I can see a direct comparison of the two images before and after upload.
@ssddanbrown commented on GitHub (Jun 5, 2021):
Since there's been no follow-up I'm going to close this. If the issue remains and is something you still require to be fixed please open a new issue, referencing this one and addressing the latest request on this issue.