# Dimension of the segmented image changes

**URL:** <https://discourse.slicer.org/t/dimension-of-the-segmented-image-changes/27284>\
**Category:** Support\
**Created:** [January 17, 2023, 4:11am UTC](https://discourse.slicer.org/t/dimension-of-the-segmented-image-changes/27284 "2023-01-17T04:11:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aditya\_Kamath](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/aditya_kamath/32/16733_2.png) [@Aditya\_Kamath](https://discourse.slicer.org/u/Aditya_Kamath)\
**Post date:** [January 17, 2023, 4:11am UTC](https://discourse.slicer.org/t/dimension-of-the-segmented-image-changes/27284/1 "2023-01-17T04:11:35Z")

</div>

Version: 4.13.0

After I segment my images when I save the image the dimensions of the segmented image change.  
Say my imaging volume is (30,192,256) My segmented image becomes (11,56,65).  
Is there any chance I could retain the exact dimensions(30,192,356) of the segmented image?

---

<div class="post-metadata">

**Author:** ![Aditya\_Kamath](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/aditya_kamath/32/16733_2.png) [@Aditya\_Kamath](https://discourse.slicer.org/u/Aditya_Kamath)\
**Post date:** [January 17, 2023, 4:52am UTC](https://discourse.slicer.org/t/dimension-of-the-segmented-image-changes/27284/2 "2023-01-17T04:52:17Z")

</div>

I figured out how that could be rectified. While saving the segment make sure you save it as .nrrd instead of .seg.nrrd. By doing so the segmented image retains the dimensions of the image volume.

---

<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:** [January 17, 2023, 5:33am UTC](https://discourse.slicer.org/t/dimension-of-the-segmented-image-changes/27284/3 "2023-01-17T05:33:34Z")

</div>

Older Slicer versions crop segmentations to minimum necessary size during saving. We thought it made no sense to save empty image regions, since we expected that all medical image computing software do all processing in physical space anyway.

However, we later learned that there are just too many software (mostly prototype code, research software, etc.) that require exact match in voxel space (not just in physical space), so we changed the default and in current Slicer versions cropping is disabled by default.

The easiest solution is to use a current Slicer version (latest Slicer Stable Release or latest Slicer Preview Release).