# Web Clipper Screenshot function is buggy

**URL:** <https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599>\
**Category:** Support\
**Created:** [7 June 2019 21:12 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599 "2019-06-07T21:12:58Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![desk7](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@desk7](https://discourse.joplinapp.org/u/desk7)\
**Post date:** [7 June 2019 21:12 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/1 "2019-06-07T21:12:58Z")

</div>

When I make a screenshot, the image in Joplin reproduce a smaller portion of the actual screenshot. For example, from this page [here](https://math.stackexchange.com/questions/86217/finding-coefficients-of-a-double-fourier-series?newreg=de67ba03567849718b8bf8570257e1ef)  
I selected this  
 ![image](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/2X/9/90461281015cf48b21ca35469d1a14841bb1e42b.png)  
and I obtained this:  
 ![7999dc27623dab8e90a1668cf9da942d](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/2X/4/443078bebd27019535e0691fa34f38b974a17d94.jpeg)  
Note that the problem doesn’t lie in visualization because I saved the image from Joplin and it’s wrong anyway.

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [8 June 2019 00:13 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/2 "2019-06-08T00:13:09Z")

</div>

What browser?

What’s the zoom level on the page? Is it 100% or something else?

---

<div class="post-metadata">

**Author:** ![desk7](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@desk7](https://discourse.joplinapp.org/u/desk7)\
**Post date:** [8 June 2019 15:43 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/3 "2019-06-08T15:43:42Z")

</div>

- Windows 10 1903
- Google Chrome 75.0.3770.80 (64 bit)
- 100% zoom level
- ad-block disabled
- Web-Clipper ver. 1.0.14
- Joplin ver. 1.0.158

* * *

I tried to install Chrome and Joplin in Windows Sandbox (actually a fresh VM) and the problem is still there.

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [10 June 2019 23:40 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/4 "2019-06-10T23:40:19Z")

</div>

I can’t replicate it but I think it might be due to this bug:

[https://bugs.chromium.org/p/chromium/issues/detail?id=415297](https://bugs.chromium.org/p/chromium/issues/detail?id=415297)

Do you have a high resolution screen, like 4K?

---

<div class="post-metadata">

**Author:** ![desk7](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@desk7](https://discourse.joplinapp.org/u/desk7)\
**Post date:** [11 June 2019 07:46 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/5 "2019-06-11T07:46:13Z")

</div>

I have a notebook with Full-HD screen with Windows default scaling to 150%.

 ![image](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/2X/f/ff18330f74607b7dda91db3f26e9c07a9142bf08.png)  
I’ve just tried to set scaling to 100% in Windows Setting and now it works well, even if screenshot is a bit blurry, it has low resolution.  
 ![3b18c3f859471c5f776118d81197474c](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/2X/9/9871d2da37afb6105c69fccdbd651b73b16d055d.jpeg)

But I can’t keep these settings. Text in Windows and apps is too small.

So the problem is in Chrome, right?

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [11 June 2019 08:27 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/6 "2019-06-11T08:27:56Z")

</div>

It seems to be a Chrome bug indeed, but maybe we can go around it by detecting the screen characteristics and getting the clipper to scale the screenshot. Did you try in Firefox by any chance?

---

<div class="post-metadata">

**Author:** ![desk7](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@desk7](https://discourse.joplinapp.org/u/desk7)\
**Post date:** [11 June 2019 08:57 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/7 "2019-06-11T08:57:14Z")

</div>

I’ve just installed Firefox and Joplin in a fresh Windows 10 1903 VM. Even if scaling was set to 125%, the screenshot is not cropped. However, it still is low-resolution. So the problem of low-resolution (or blurry effect I don’t know) is always present. To compare, see side by side the screenshot made by Joplin and the screenshot made by Windows:

 ![a449ad318c18b679ece927b9e55f418d](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/2X/5/5f173402f757d94d497dc13e279e4d04c06e7b73.jpeg)  
 ![Immagine](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/2X/7/72f1867444c05667e7e355d9c991beb47bc33a46.png)

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [11 June 2019 12:00 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/8 "2019-06-11T12:00:01Z")

</div>

The image is not blurry, it’s just lower resolution. I guess Windows capture the image at 150% while Firefox just captures it at 100%. There’s not much we can do here as we can only work with what the browser API provide. Perhaps one way to get a higher resolution image would be to scale your browser to 150% too.

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [11 June 2019 12:19 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/9 "2019-06-11T12:19:50Z")

</div>

Do you have the “Advanced Scaling settings” on your laptop?

![](https://winaero.com/blog/wp-content/uploads/2017/12/advanced-scaling-settings.png)

And does it work any better if you enable it?

---

<div class="post-metadata">

**Author:** ![desk7](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@desk7](https://discourse.joplinapp.org/u/desk7)\
**Post date:** [11 June 2019 13:59 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/10 "2019-06-11T13:59:11Z")

</div>

Thanks for answer. Unfortunately “Let Windows solve scaling problem” is already enabled.

---

<div class="post-metadata">

**Author:** ![desk7](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@desk7](https://discourse.joplinapp.org/u/desk7)\
**Post date:** [11 June 2019 16:22 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/11 "2019-06-11T16:22:34Z")

</div>

Just to give you some information, I tried a couple of way to take screenshots so that we can compare with Joplin. All of these with 125% scaling (like before)

1. Screenshot with Joplin in Firefox  

2. Screenshot with Joplin in Chrome  

3. Screenshot in Firefox with Firefox Screenshot  

4. Screenshot in Chrome with devtools  

5. Screenshot in Chrome with Lightshot extension  

As you can see, there are difference in cropping and resolution. In Chrome devtool and another extension have no problem

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [12 June 2019 08:14 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/12 "2019-06-12T08:14:10Z")

</div>

Setting my desktop at 125% I can’t replicate this, so I guess a Full-HD screen is needed but since I don’t have one, I won’t be able to fix this at the moment.

---

<div class="post-metadata">

**Author:** ![vb0](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/vb0/32/1299_2.png) [@vb0](https://discourse.joplinapp.org/u/vb0)\
**Post date:** [18 August 2019 08:21 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/13 "2019-08-18T08:21:05Z")

</div>

I’m having the same on a 4k monitor with “Advanced scaling” set to 150%.

---

<div class="post-metadata">

**Author:** ![theerror](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/theerror/32/303_2.png) [@theerror](https://discourse.joplinapp.org/u/theerror)\
**Post date:** [10 February 2020 11:27 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/14 "2020-02-10T11:27:41Z")

</div>

same shit story on my side as well. It’s so annoying and long bug. I’m using Mac and Chrome.

I’m wiling to do every test, it would need. It’s so annoying… ;(

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [10 February 2020 15:17 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/15 "2020-02-10T15:17:25Z")

</div>

I seem to remember there’s a Chrome and/or Firefox bug report about this. Anyone knows what’s the status of it?

---

<div class="post-metadata">

**Author:** ![theerror](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/theerror/32/303_2.png) [@theerror](https://discourse.joplinapp.org/u/theerror)\
**Post date:** [14 August 2020 13:27 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/16 "2020-08-14T13:27:19Z")

</div>

What I know, status is, that it’s still not working to me. I’m not aware of bugissue. however… Should I create one?

---

<div class="post-metadata">

**Author:** ![desk7](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@desk7](https://discourse.joplinapp.org/u/desk7)\
**Post date:** [14 August 2020 15:46 UTC](https://discourse.joplinapp.org/t/web-clipper-screenshot-function-is-buggy/2599/17 "2020-08-14T15:46:24Z")

</div>

AFAIK the WebClipper bug in Chrome is still there. In Firefox it works well. I don’t know about the Chrome bug report which @laurent referes to. In fact, as you can see in my post, Chrome devtools and another extension (Lightshot extension) have no issue in making screenshot. So I would think the problem is in the WebClipper itself.