# CT slices are not stacked on top of each other

**URL:** <https://discourse.slicer.org/t/ct-slices-are-not-stacked-on-top-of-each-other/2299>\
**Category:** Support\
**Created:** [March 12, 2018, 3:49pm UTC](https://discourse.slicer.org/t/ct-slices-are-not-stacked-on-top-of-each-other/2299 "2018-03-12T15:49:57Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [March 12, 2018, 3:56pm UTC](https://discourse.slicer.org/t/ct-slices-are-not-stacked-on-top-of-each-other/2299/2 "2018-03-12T15:56:07Z")

</div>

By default Slicer shows standard axial, sagittal, coronal oriented slices. If your volume is not axis-aligned and the spacing between slices is very large then you may get staircase appearance.

For non-axis-aligned acquisitions, you may want to show the slices in their native orientation, by [using “Rotate to volume plane” function](https://discourse.slicer.org/t/mri-dwi-images-load-with-wrong-orientation/482/2?u=lassoan).

If you want to process a volume that has highly anisotropic spacing (e.g., 10x larger spacing between slices than spacing between pixels within a slice) and you want to process it (segment, register, etc.) then it is strongly recommended to crop&resample the volume to have isotropic spacing, using Crop volume module.

---

_[View the full topic](https://discourse.slicer.org/t/ct-slices-are-not-stacked-on-top-of-each-other/2299)._