# Issue with NIfTI Image Orientation After DICOM Conversion

**URL:** <https://discourse.slicer.org/t/issue-with-nifti-image-orientation-after-dicom-conversion/31792>\
**Category:** Support\
**Created:** [September 19, 2023, 4:14pm UTC](https://discourse.slicer.org/t/issue-with-nifti-image-orientation-after-dicom-conversion/31792 "2023-09-19T16:14:40Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![mikebind](https://avatars.discourse-cdn.com/v4/letter/m/71e660/32.png) [@mikebind](https://discourse.slicer.org/u/mikebind)\
**Post date:** [January 27, 2024, 12:16am UTC](https://discourse.slicer.org/t/issue-with-nifti-image-orientation-after-dicom-conversion/31792/11 "2024-01-27T00:16:13Z")

</div>

If you are using FSL FLIRT, the post below might also be helpful. Slicer and FSL think about transformation matrices and coordinate systems differently, and you can’t just use an FSL transformation matrix in Slicer and expect it to do what you want. It took me a while to figure out the exact relationship between them, but I hope this can be helpful to you:

> [@Importing FSL FLIRT transformation matrices?](https://discourse.slicer.org/t/importing-fsl-flirt-transformation-matrices/30819/8):
>
> Quick Summary It is possible to convert between Slicer registration transform matrices and FSL/FLIRT registration transform matrices. They differ because Slicer transforms describe transformations within RAS space, whereas FLIRT transforms describe transformations between scaled (and sometimes reflected) voxel spaces. Converting between them requires understanding exactly when FLIRT transforms performed a reflection/translation before registration, as well as what other elements of the images …

---

_[View the full topic](https://discourse.slicer.org/t/issue-with-nifti-image-orientation-after-dicom-conversion/31792)._