# Save screenshot in JPG format misbehaves

**URL:** https://discourse.paraview.org/t/save-screenshot-in-jpg-format-misbehaves/17310
**Category:** ParaView Support
**Created:** [November 15, 2025, 9:20pm UTC](https://discourse.paraview.org/t/save-screenshot-in-jpg-format-misbehaves/17310 "2025-11-15T21:20:13Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![mckel](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mckel/32/6435_2.png) [@mckel](https://discourse.paraview.org/u/mckel)
#### Post date: [November 15, 2025, 9:20pm UTC](https://discourse.paraview.org/t/save-screenshot-in-jpg-format-misbehaves/17310/1 "2025-11-15T21:20:13Z")

</div>

Dear all,

in ParaView 6.0.1 running on Windows 11 I have a problem with the Save Screenshot functionality when the saved image is of JPG type. It appears that the image format is not recognized properly as JPG.

How to reproduce?

- ParaView GUI:
  - Setup a render view

  - File → Save Screenshot

  - Set jpg file name, e.g., test.jpg

  - The “Save Screenshot Options” menu will look like this:

  - Note that under “Image Options” the format is set to PNG and png-specific option “Compression Level” is shown

- Python Shell
  - Setup a render view

  - View → Python Shell

  - Enter: `SaveScreenshot(filename="test.jpg",Quality=90)`

  - The following error message is thrown:

  - Note that `Quality = 90` is not accepted as valid parameter as it is only expected if the image format is JPG and latter apparently is not properly identified from the file name `test.jpg`.

Is this a bug or am I missing something here?

Best regards,  
mckel

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 17, 2025, 9:26am UTC](https://discourse.paraview.org/t/save-screenshot-in-jpg-format-misbehaves/17310/2 "2025-11-17T09:26:17Z")

</div>

I’m unable to reproduce with ParaView 6.0.1 binary release on Linux.

---

<div class="post-metadata">

### Author: ![mckel](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mckel/32/6435_2.png) [@mckel](https://discourse.paraview.org/u/mckel)
#### Post date: [November 17, 2025, 2:21pm UTC](https://discourse.paraview.org/t/save-screenshot-in-jpg-format-misbehaves/17310/3 "2025-11-17T14:21:28Z")

</div>

Thanks for checking! Indeed, I am not able to reproduce this on Linux either. But the issue still persists on Windows. I tested with 6.0.0 and 6.0.1. With 5.13.3 it is properly working.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 18, 2025, 9:48am UTC](https://discourse.paraview.org/t/save-screenshot-in-jpg-format-misbehaves/17310/4 "2025-11-18T09:48:44Z")

</div>

Unable to reproduce with ParaView 6.0.1 using Windows binary release.

---

<div class="post-metadata">

### Author: ![mckel](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mckel/32/6435_2.png) [@mckel](https://discourse.paraview.org/u/mckel)
#### Post date: [November 19, 2025, 1:59pm UTC](https://discourse.paraview.org/t/save-screenshot-in-jpg-format-misbehaves/17310/5 "2025-11-19T13:59:52Z")

</div>

Originally, I was referring to the MSI installer release. However, I have now tested the Windows binary release ParaView-6.0.1-MPI-Windows-Python3.12-msvc2017-AMD64.zip on two Windows systems. On the one system the problem further exists, on the other system the problem does not occur.

Unfortunately, still don’t know the cause for this. As it is system-specific probably difficult to find out. Any ideas?

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 19, 2025, 2:05pm UTC](https://discourse.paraview.org/t/save-screenshot-in-jpg-format-misbehaves/17310/6 "2025-11-19T14:05:26Z")

</div>

> [@mckel](#):
>
> On the one system the problem further exists, on the other system the problem does not occur.

Did you test with the .msi or the .zip ? that is not clear to me.

---

<div class="post-metadata">

### Author: ![mckel](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mckel/32/6435_2.png) [@mckel](https://discourse.paraview.org/u/mckel)
#### Post date: [November 19, 2025, 5:31pm UTC](https://discourse.paraview.org/t/save-screenshot-in-jpg-format-misbehaves/17310/7 "2025-11-19T17:31:45Z")

</div>

I did the tests today with the zip download, on both mentioned systems.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 20, 2025, 8:54am UTC](https://discourse.paraview.org/t/save-screenshot-in-jpg-format-misbehaves/17310/8 "2025-11-20T08:54:12Z")

</div>

Can you check difference in Windows version ?  
Can you reset your ParaView settings ?

---

<div class="post-metadata">

### Author: ![mckel](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mckel/32/6435_2.png) [@mckel](https://discourse.paraview.org/u/mckel)
#### Post date: [November 20, 2025, 11:43pm UTC](https://discourse.paraview.org/t/save-screenshot-in-jpg-format-misbehaves/17310/9 "2025-11-20T23:43:05Z")

</div>

Wow, resetting ParaView settings solved the issue. Thank you for the hint!
