# Extract .jpg from DICOM file

**URL:** <https://discourse.slicer.org/t/extract-jpg-from-dicom-file/17873>\
**Category:** Support\
**Tags:** dicom\
**Created:** [May 31, 2021, 12:51am UTC](https://discourse.slicer.org/t/extract-jpg-from-dicom-file/17873 "2021-05-31T00:51:38Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 31, 2021, 9:39pm UTC](https://discourse.slicer.org/t/extract-jpg-from-dicom-file/17873/3 "2021-05-31T21:39:28Z")

</div>

Saving as JPG is good if you want get the image slices so that you can show them in a powerpoint presentation (and then Screen Capture module is a perfect tool).

However, if you are thinking about saving a CT image as JPG for deep learning (because the example/tutorial that you would like to try uses JPG as input) then I would recommend to look a bit further, because you can lose clinically significant information by converting a CT-image to a 8-bit JPG image. See some more information and alternatives in many other similar posts in this forum - for example this one:

> [@How to export slices into system without loosing information](https://discourse.slicer.org/t/how-to-export-slices-into-system-without-loosing-information/17532/11):
>
> There is certainly nothing revolutionary about nrrd, it just does what it is designed for - storing 2D/3D/4D images in 3D space with various scalar types and bit depth, with known origin, spacing, and axis directions. We try to steer users away from using png and other consumer file formats because they are not designed for storing medical images and they do a very bad job at that: they cannot store 3D information, physical size, position, orientation, only support a few pixel types, etc. Have…

---

_[View the full topic](https://discourse.slicer.org/t/extract-jpg-from-dicom-file/17873)._