# How to handle CT intensity / contrast differences

**URL:** <https://discourse.slicer.org/t/how-to-handle-ct-intensity-contrast-differences/19604>\
**Category:** Support\
**Created:** [September 10, 2021, 9:35am UTC](https://discourse.slicer.org/t/how-to-handle-ct-intensity-contrast-differences/19604 "2021-09-10T09:35:20Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [September 11, 2021, 12:42am UTC](https://discourse.slicer.org/t/how-to-handle-ct-intensity-contrast-differences/19604/5 "2021-09-11T00:42:21Z")

</div>

See some more information on how to adjust window/level:

> [@Recent improvements in window/level management](https://discourse.slicer.org/t/recent-improvements-in-window-level-management/7284):
>
> This is a quick summary of image window/level (brightness/contrast) adjustment changes introduced in recent Slicer Preview (formerly known as “Nightly”) releases. Improved automatic window/level algorithm Images that do not contain preferred window/level information are displayed with automatically computed values. The complex automatic computation algorithm that had been used in Slicer worked marginally better for some images, but sometimes generated too bright images and overall the results…

I’ve fixed the DICOM import plugin now to [use the middle slice’s window/level instead of the first file’s](https://github.com/Slicer/Slicer/issues/5140). @rbumm It would be great if you could test the Slicer Preview Release tomorrow if the default window/level setting works better.

---

_[View the full topic](https://discourse.slicer.org/t/how-to-handle-ct-intensity-contrast-differences/19604)._