# Load Failed over multiple formats (TIFF, NRRD) **URL:** \ **Category:** Support\ **Created:** [August 29, 2026, 11:45pm UTC](https://discourse.slicer.org/t/load-failed-over-multiple-formats-tiff-nrrd/48018 "2026-08-29T23:45:45Z")\ **Posts on this page:** 1\ **Showing post:** 3

**Author:** ![asims](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@asims](https://discourse.slicer.org/u/asims)\ **Post date:** [August 30, 2026, 12:08am UTC](https://discourse.slicer.org/t/load-failed-over-multiple-formats-tiff-nrrd/48018/3 "2026-08-30T00:08:27Z")

I have since found out a little more. The NRRD image is approx 20GB. I am running on a system with over 60GB. On a previous read attempt, error messages regarding memory appeared. In this case other hanging processes from image conversion had used up the memory. With those processes terminated, Slicer successfully loads the file into memory but takes a long time about it. This discussion can be closed. Seems like there might have been some issue with the TIFF volume not matching format. Conversion to NRRD has worked. I think the dataset can probably be reduced. Bit depth if nothing else. I came across the discussion here in 2024 that was helpful. > [@Bad performance when segmenting 11GB micro-CT](https://discourse.slicer.org/t/bad-performance-when-segmenting-11gb-micro-ct/38362/2): > > There are many ways to improve the performance. But first you have to understand the memory usage during segmentation. If your volume is 11GB in size, during the segmentation (depending on the effect), Slicer may use 6-10 times more (so 60-100GB) transiently. That’s already at the limit of available memory on your computer. Adding another segment or five will increase even further. So while your computer is fairly powerful, your dataset is also quite big. There are many ways to deal with that. … --- _[View the full topic](https://discourse.slicer.org/t/load-failed-over-multiple-formats-tiff-nrrd/48018)._