# Saving segmentation as DICOM

**URL:** <https://discourse.slicer.org/t/saving-segmentation-as-dicom/21576>\
**Category:** Support\
**Tags:** segmentation, dicom\
**Created:** [January 22, 2022, 3:55pm UTC](https://discourse.slicer.org/t/saving-segmentation-as-dicom/21576 "2022-01-22T15:55:11Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![WojtekL](https://avatars.discourse-cdn.com/v4/letter/w/67e7ee/32.png) [@WojtekL](https://discourse.slicer.org/u/WojtekL)\
**Post date:** [February 7, 2022, 2:19pm UTC](https://discourse.slicer.org/t/saving-segmentation-as-dicom/21576/7 "2022-02-07T14:19:59Z")

</div>

Hello,

thank you for the answer. I do have the Quantitaive Reporting extension installed and I managed to succesfully export the segmentation to DICOM SEG.

After doing so, I only encountered the issue described in the following thread [https://discourse.slicer.org/t/matching-segmentation-with-the-input-data/21817](https://discourse.slicer.org/t/matching-segmentation-with-the-input-data/21817)

Do you know why a situation described in the thread above happens? @cpinter

Thank you

---

_[View the full topic](https://discourse.slicer.org/t/saving-segmentation-as-dicom/21576)._