Force RGB mode in Mac OS X to fix the picture quality of an external monitor

I recently bought a MacBook Pro (with ‘Retina’ screen), but when I hooked it up to my Dell U2410 monitor via HDMI cable I was shocked by the poor picture quality. The contrast was all wrong and text was misshapen. No amount of calibration in the monitor or software would fix it.

Short answer: OS X thinks my monitor is a TV, and is using the YCbCr colour space rather than RGB. I had to override an EDID setting to force the RGB colour space, and it is now working correctly.

Long answer: I haven’t owned a Mac for a while and had forgotten how difficult much of the “Apple community” can be when it comes to anything that can’t be adjusted in System Preferences. Googling for problems with external monitors on MacBooks found dozens of threads on official and unofficial Apple forums, all full of people with the same problem. The most common response was to blame the monitor, despite assurances from the stricken users that the monitor worked beautifully in Linux and Windows, even on the same machine under Boot Camp.

“You just haven’t calibrated it!”, “You are just too used to Retina now!”, “You just need to buy a Thunderbolt display!” Apple people also like to solve problems by throwing more money at it. (I realise that owning a Mac makes me an Apple person, too. Hypocritical self-loather?)

My lucky break was reading that the current colour space was “YCbCr” when I was browsing the monitor’s settings menu. I was sure that it was using RGB when hooked up to my PC, so I started searching instead for forcing RGB mode in OS X. It didn’t appear to be available out-of-the-box, but I have had some experience in overriding EDID settings for similar purposes so I searched instead for that.

I found this thread on the forums. Mr Schwarz, thanks very much. Your thread and script was incredibly helpful and informative. It was written to fix problems connecting an external monitor via DisplayPort, but it fixed my HDMI issue just the same. I’ve summarised the required steps below.

My last word is to wonder what Apple is playing at. It seems that this problem has been reported by a lot of people for a long time, and I expect it would require a fairly simple software update. Do they just not care about those using third-party components, or are they actively attempting to force people on to Thunderbolt displays?

How to force RGB in Mac OS X

These steps have been updated for Mac OS version 10.11, “El Capitan”. See below for differences for previous versions of the system.

  1. Download the patch-edid.rb script from the forums thread above, or download Andrew Daugherity’s improved patch-edid.rb script from his github page. Put the script in your home directory.
  2. Disable “rootless” mode, you can follow these instructions: How to modify System Integrity Protection in El Capitan.
  3. Reboot.
  4. Connect only the external monitor(s) in question, if you can (I closed my MacBook lid, for example). The script will make override files for any connected monitor.
  5. Type “ruby patch-edid.rb” in Terminal.
  6. A new folder will be created in your home directory. Move it into the “/System/Library/Displays/Contents/Resources/Overrides” folder. You may have to create the Resources and Overrides folders. If Finder tells you that you are overwriting an existing folder, consider backing it up first.
  7. Restart your computer. The picture quality should be fixed from this point.
  8. Re-enable “rootless” mode, the instructions are available on the same guide: How to modify System Integrity Protection in El Capitan.
  9. Reboot. Enjoy your monitor.

To undo the changes, either delete the folder you had copied to the Overrides folder (if it didn’t already exist) or replace it with the folder you had backed up. You will need to re-enable rootless mode to do this.

Earlier versions of Mac OS X

The process is a little more straightforward. There are two differences to the steps above:

  1. You do not need to disable/re-enable rootless mode and perform the subsequent reboots.
  2. The overrides folder location is “/System/Library/Displays/Overrides”.


I no longer own a Macbook Pro, but if you’re having trouble with any of these steps, please have a look through the comments below (and note that there are multiple pages). Many questions have been answered with helpful tips from others.

Update, 20 Nov 2016: In the comments Marcus has proposed a faster method that doesn’t require SIP to be disabled. Others have had success with it so give it a go if you’re uncomfortable with disabling SIP.

Update, 8 Feb 2016: A comment from nos1609 below, warns about a bootloop that can occur when running other patches (like the pixel-clock patch) simultaneously, and how to get around it.

Update, 23 Nov 2015: According to Peter’s post, you don’t need to disable SIP if you use recovery mode. If others have similar success with this method I’ll update the process.

Update, 3 Oct 2015: I have amended this post to target El Capitan. I have taken the steps from bigmcguire’s process, posted in the comments. Although some are still having issues, it appears to be working for people. Thanks!

Update, 29 May 2015: Mac OS 10.11 El Capitan does things a little differently. You must first disable the new ‘rootless’ mode and then use a different overrides folder: /System/Library/Displays/Contents/Resources/Overrides. Rootless can then be re-enabled if desired, as confirmed by nos1609 in the comments below. El Capitan is still in beta, I’ll update this post if the issue is still apparent afterwards.

Update, 26 May 2014: If you have had trouble with limited resolutions being available after the fix, check out Ibrahim’s comments here.

Update, 28 Nov 2013: If the process appears to work but doesn’t seem to make a difference, consider Tom’s comments below. Depending on your monitor an extra tweak may be required.

Update, 13 Nov 2013: Andrew comments below that he has modified the script to add some useful new features, and provides a link to his GitHub for those wishing to use it instead.

Update, 27 Oct 2013: If you’ve applied this fix before, the OS X Mavericks update will overwrite it. I’ve successfully re-applied the fix by following exactly the same steps, and other commenters below have done so, too.

945 thoughts on “Force RGB mode in Mac OS X to fix the picture quality of an external monitor

  1. Thanks Guys. NOTE: for me it only worked after I did the “sudo ruby ….”. Without the super user the script was giving an error in El Capitain.

  2. I also have a Dell U2410, and a late 2013 MacBook Pro running El Capitan. Both the script and the resulting file and folder appear readable, yet, I see no changes. Any ideas why it’s not working for me?

    • In System Report under Graphics/Displays, does it still say “Television: Yes” under the Display section? If yes, then your patch didn’t get applied correctly. If no, you may need SwitchResX as I did (see my other post).

    • I’m having the same problem… It used to work just fine but since updating to the latest version of OS X (Still El Cap not Sierra beta) it doesn’t seem to be working anymore.

  3. Wow thank you, this has been incredibly helpful! I am using a 13″ macbook air 2015 and had been getting black borders around my desktop image on two different LG widescreen monitors. Now, they are gone.

  4. Single Link DVI and old school HDMI 1.0-1.2 connections are limited to 1920 x 1200, so you folks with higher resolution DVI connected monitors need a dual-link DVI connection. DisplayPort connections can be much higher, but be aware there are version 1.0, 1.1, 1.2, 1.2a, 1.3, 1.4.

  5. Adding my thanks for this post. I have a 29″ AOC (standard res) monitor to which I’ve employed this fix over several system updates, and it has worked every time, including the most recent El Capitan version. I can confirm the poor display quality issue is not due to resolution settings, font smoothing, calibration, or drivers (AFAIK none is available in my case — not sure if any of AOC’s monitors is designed to work with Mac systems). I used the disable/enable SIPS process but skipped the second-to-last reboot.

  6. I had to use this along with ScreenResX to get things sorted, but my two LG 29UC97C-B displays are working beautifully now. Thank you very much!!

    • Why did you have to use switchResX and what did you do? I’ve tried this fix on my iMAc Retina, and the Dell 2407 connected to it via thunderbolt and DVI is resolutely fuzzy

      • The patch corrected the problem of OS X recognizing the displays as televisions, but the picture quality didn’t change for me. After installing SwitchResX and using the settings exactly as described by genriquediaz at, then the picture quality was perfect. FYI, my graphics card has two DVI dual-link connections and I’m using a DVI-I Dual-Link to HDMI adapter and connecting the other end of the HDMI cable to the displays. I’m using 2560×1080 resolution.

    • Yes it does, thankfully. I did have to turn root off to copy the folder to the correct directory, then turn it back on.

  7. I am trying to connect a rMBP running Yosemite to a Dell U2414H monitor. I have tried everything mentioned here, created the new profile etc. I can see the new profile being used in Displays setting but the fonts are still fuzzy. I have tried with HDMI-HDMI and mini DisplayPort-DisplayPort connections. That does not help either. Does anyone have any more ideas?

    • Seems better after reset the monitor. But still, Mac has many problem not solved, ui, shortcut, etc, I buy mac for developing ios, dunno why many people like apple stuff, I prefer linux or windows. :(

    • I have an Asus VN279QLB and also having the exact same problem as described above.

      Tried the patch and it appears to have worked, but no change in the display.

      I’ve used HDMI with many other monitors fine, so very confused.

  8. Tried it on my 4K Benq BE2420 and after the reboot I could get access to the “HDMI RGB PC Range” in the monitor OSD (it was greyed out before) and I could switch to full RGB. So much better! Thanks.

  9. Hi,

    I applied the fix to my monitor (AOC) – It didn’t seem to work (all steps completed and understood). I tried the remove/reconnect suggestion, that didn’t help. However, I then went into the monitor settings and performed a reset – bingo!


    • To be completely clear – the menu on the monitor itself – and performed a reset – not any setting on MAC OS X.

  10. This didn’t work for me, when i run the script i get this message:

    patch-edid.rb:9:in `scan’: invalid byte sequence in UTF-8 (ArgumentError)
    from patch-edid.rb:9:in `’

    How can i fix this?

  11. I have a Dell S2415H connected to a 13″ Retina Macbook Pro (Early 2016) running El Capitan 10.11.4.
    I did the following steps to fix the blurry text which was driving me crazy:
    1. Put the macbook in Clamshell mode
    2. Run the ‘Force RGB’ patch
    3. Set Display Profile to ‘Color LCD’
    4. Reset the monitor’s settings to default.
    5. run this command on terminal ‘defaults -currentHost write -globalDomain AppleFontSmoothing -int 3’ and reboot the macbook.

    • Thanks for the font smoothing trick. The font smoothing trick looked promising until I noticed that the apple menu, finder etc (apple related) were fine but other applications like firefox, intellij idea were all too bold. Is there a way to keep the apple related with font smotthing 3 and other applications to a lesser value like 2 or something?

      At the rate my 1080p Lenovo displays, I think I am going to go blind in few days

  12. apologies. I also later noticed that the string for the Dell U2410 had some weird characters. I modified the file using vi text editor and all good now. After rebooting, the input colour format on the dell colour settings is now RGB. finally!. However, i notice no improvement. the quality and colours are very very good as before. Did I have to do this?

  13. I have a mac mini MAC OS X 10.7.5 using HDMI cable to DEL U2410. I tried running this script and copied to Overrides folder. It makes no difference, Dell monitor settings for colour settings colour input mode still shows heavy green hue if I set it to RGB and I’m forced to keep it a YPbPr.

  14. Executed the procedure as explained but was not successful with my setup. Using a MBpro with HDMI-HDMI on a BENQ GL2450H. Override is working correctly but the font is still blurry. Looks like I have to switch to DVI as a lot of people saying this works better for them.

    Anyway, thanks for your efforts working on this patch.


  15. I have an early 2011 Macbook Pro 15″ running Mavericks connected to a LG 23MP47HQ-P IPS monitor. It is connected through a thunderbolt to HDMI adapter and is being recognized as a TV. I’ve run the patch multiple times with no success. I’ve gone into the Display Vendor ID file and the LG monitor is being recognized and has the correct name in the code. I’ve also tried to edit the display name in the patch file (as per Michiel’s comment) before running the terminal command but this causes an error in the execution and doesn’t create a new folder.

    Would anyone have any other ideas of what might solve my issue. Did I buy a monitor that this patch just will not work on?


  16. Can anyone help me with instructions to “Put the script in your home directory.” Not sure what that means. I assume that is NOT the same as “Home folder”. Please assist. THANK YOU!

    • It’s exactly what you read, in finder find your home directory is your name on the left hand side. the icon is like a house. Hope it helps…

  17. Dudes! I can now use my MBPr “13” with my Dell 2414H Ultrasharp (previously Ultra-fuzzy) for more than just web surfing. It’s crazy how much better everything looks with this fix. Thanks to all who put time and effort into explaining this.

  18. If anybody is planning using this patch in combination with pixel-clock patch one has to keep in mind, that prior using pixel-clock there is the need to remove any previous RGB patches. So every custom folder added to Overrides directory should be removed, then apply the pixel-clock patch, and finally the patch-ede one.

    Otherwise, you’ll face a bootloop like this one

    PS Confirmed working on mac mini 2012 MD388 with two dell u2913wm over HDMI and USB with freed up thunderbolt port for any other use at their full res on El Capitan 10.11.4 Beta 2 (15E33e), so the code of improved script remains still up to date. Many thanks!

  19. I have a BenQ XL2720Z monitor hooked up via displayport to my 2015 Macbook Pro with AMD graphics running El Capitan. When I patch the EDID I lose the 144hz refresh rate and get only 60hz.

  20. Hello,
    Many thanks for your detailed instructions.
    I have copied the executed file into the Overrides folder, renaming the folder to be the same as one of the original ones as suggested in the comments. Despite restarting this does not appear to have improved the blurriness of the text. Is there anything else I can do?

  21. I’m extremely grateful for your detailed email! I just upgraded to a newer MacBook Pro and was fighting grainy text and dull colors. This worked like a charm!

    • Hello, I just purchased an Acer K272HL monitor and I trying to improve the picture quality. I am not an IT Guru therefore would appreciate a simplified version of resolving this problem. Thanks in advance.

  22. It wasn’t working for me so after some intense digging around I found out that you might need to disconnect and reconnect the monitor. Worked for me!

  23. Unbelievable how much this changes the clarity! Thank you so much, I would’ve never figured this out.

    Monitor: HP 27xw Display


  24. I can say that although it is much better with RGB now. Text is still not as good as neither on mb pro retina display nor on my monitor connected to windows pc.

  25. I confirm this solution worked for my setup: late 2013 mbp retina with El Capitan + U2715H connected via hdmi. Now my monitor shows the input as RGB and there is a significant improvement in image quality. Although it is now ok quality I am not sure if it is still as good as connecting my windows pc though. Maybe I should play with font smoothing.

    Btw, I did not try Peter’s method because I did not see it until I complete the fix :) Maybe you can put an information about that up in the instructions.

    Thanks a lot!

  26. A million thanks, was about to order a way overpriced cable from the applestore but now i can finally code for real with my Dell U2913WM THANKS!

  27. Hello! I am so frustrated. I did it once before El Captain… I got El Capitain now, and i am back to the pink/green philips screen every couple of minutes.

    I tried it again, but it doesn’t work this time. Here is whats not working:

    Type “ruby patch-edid.rb” in Terminal. – causes:

    ruby: No such file or directory — patch-edid.rb (LoadError)

    so i can’t find a new folder. :-(

    Besides i am not sure about the script writing thing. how to do it with my macbook.

    Please, anyone can help me?

    Thank you, Jana

    • Still hoping for anyone to help me out. I tried anything… Please anyone help me. :-( already thinking about being an old macbook to use with the Philips.

        • Dmitry -> thank you!!! I went to finder and typed ~/ … Or what do you mean by “get”? I am just a stupid user. ;-)

          On Thursday I planned on bying an old mac book :-( to be able to use the Philips again…

  28. Hello there. I have made severalattempts and the image quality is still nowhere near how it shows on windows via virtualbox.

    Using: macmini end 2012
    Screen: ASUS VX248 24”

    Does anyone have any tips?

Leave a Reply