1920x1080 vs 1920x1200 -- Text readability.


Recommended Posts

Hi, I'm trying to decide between a 24" 1920x1080 monitor (16:9) and a 24" 1920x1200 monitor (16:10). My main focus is text readability... I stare at text all day and so that's the most important thing to me.

Do more vertical pixels in the same size monitor mean everything, including text, is smaller, or is the 1920x1200 actually taller vertically than the 1920x1080, to make up for the higher vertical resolution?

I'm a bit confused. :)

You already answered it yourself. It's simply taller vertically. I have a 24" 1920x1200 monitor and my laptop is HD resolution. There is no change in text readability. Arguably, it's better on the 24", because there is more space vertically so I can zoom in a little, but still get a lot of text on the screen.

I just got a 16:9 screen. Came from a 16:10. Text readability is great ( better than my 22 inch at 1680x1050). The PPI is slightly higher, resulting in a more detailed image. If you are looking for any recommendations, I'd highly recommend the NEC EA231WMi.

According to my calculations :

24" 1920x1200 pixels = 8.90 pixels / square inch

24" 1920x1080 pixels = 8.43 pixels / square inch

The more you have pixels / square inch, the smaller things are. So if you want text to be bigger, go with the 24" 1920x1080, things will be about 5% bigger, which is negligible.

Also, the new displays are all 16:9, 16:10 is the past. So 2 - 0 for the 1080p display :)

Please someone, correct me if I'm wrong...

My preference would be for 16:10. I like the vertical height. But, the other day I was using my family's new laptop with a 1920x1080 resolution, and the lack of vertical height didn't really bother me. Nonetheless, if I was buying a monitor, I would go for 16:10. I'm sure the text readability would be great on both of them.

As others have said, the pixels are "square" on pc monitors, so the same diagonal dimension with different resolutions will have different aspect ratios - nothing is stretched.

19:9 seems to be most common, and when one of my 1920*1200 died I had very few to choose from and difficulty matching my second monitor, it also seems 1920*1080 is substantially cheaper. There's not a hugely noticeable difference - especially if you are mainly using it for reading text. I use a 24inch samsung at 1920*1200 at home and a 23inch samsung at 1920*1080 at work, and the difference doesn't bother me in the slightest.

Thanks for the info guys. :)

Here's another question: since a 16:10 is obviously slightly less-wide than a 16:9 at the same screen size, do you think that a 16:10 is inferior when having multiple windows next to each other? Or is the difference negligible since the resolution is the same?

According to my calculations :

24" 1920x1200 pixels = 8.90 pixels / square inch

24" 1920x1080 pixels = 8.43 pixels / square inch

The more you have pixels / square inch, the smaller things are. So if you want text to be bigger, go with the 24" 1920x1080, things will be about 5% bigger, which is negligible.

Also, the new displays are all 16:9, 16:10 is the past. So 2 - 0 for the 1080p display :)

Please someone, correct me if I'm wrong...

Yeah, you're off by a bit, a pixel density of 8.90 pixels per square inch would result in each pixel being nearly 3mm wide and tall, there's actually 8,900 pixels per square inch, not 8.9 :p

I'm sorry but 16:9 displays are a gimmick. How much DVD and HD content is really 16:9? The truth of the matter is, you're still going to get black bars for most of what you watch anyway, so you may as well get the 16:10. More screen real estate, and the benefit of being able to fit two A4 pages side by side is awesome for reading.

The truth of the matter is, you're still going to get black bars for most of what you watch anyway, so you may as well get the 16:10. More screen real estate, and the benefit of being able to fit two A4 pages side by side is awesome for reading.

This.

I'm sorry but 16:9 displays are a gimmick. How much DVD and HD content is really 16:9? The truth of the matter is, you're still going to get black bars for most of what you watch anyway, so you may as well get the 16:10. More screen real estate, and the benefit of being able to fit two A4 pages side by side is awesome for reading.

Watching on demand TV on iPlayer, Youtube, the hundreds of podcasts out there etc. are almost always without a letterbox on 16:9. I personally prefer it. It also means if you connect it up to your games console you don't have to use a funky resolution (360 handles this pretty well, admittedly).

Yeah, you're off by a bit, a pixel density of 8.90 pixels per square inch would result in each pixel being nearly 3mm wide and tall, there's actually 8,900 pixels per square inch, not 8.9 :p

Heh yeah, I should have checked if it made sense or not. It's 8 900 XD, don't know what I did there, but it's the same proportions anyways, so it's still cool :p

I must have used kilopixels instead.... ahhh those damned kilopixels.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Samsung messages is still alive and well. They reversed that and decided to our more effort into it.
    • I think every American should have a course in a 'dry sense of humour' at school; and perhaps 'using sarcasm in jest' oh, and also 'the use or irony in humour'.
    • What they really need to do is automatically spell "loses" and "lose" correctly since nobody seems to know how to anymore. Then they blame spellcheck/autocomplete and don't realize autocomplete is just filling in the word for them automatically so it was misspelled in the first place.
    • If someone chooses to continue using SB and therefore goes through the manual intervention in the thread, afterwards the BSOD problem is gone. Whether they then re-enable the task doesn't matter, they're done, though on such machines it might pay to keep it disabled in case the next update (if there is a next) causes the same problem. OTOH, if someone disables SB in the BIOS, the problem is also gone. Incidentally, I noticed that this task exists even on machines that don't support SB. It's just installed across the board...and runs. Doing what on such machines is a little hazy.
    • qBittorrent 5.2.2 by Razvan Serea The qBittorrent project aims to provide a Free Software alternative to µtorrent. qBittorrent is an advanced and multi-platform BitTorrent client with a nice user interface as well as a Web UI for remote control and an integrated search engine. qBittorrent aims to meet the needs of most users while using as little CPU and memory as possible. qBittorrent is a truly Open Source project, and as such, anyone can and should contribute to it. qBittorrent features: Polished µTorrent-like User Interface Well-integrated and extensible Search Engine Simultaneous search in most famous BitTorrent search sites Per-category-specific search requests (e.g. Books, Music, Movies) All Bittorrent extensions DHT, Peer Exchange, Full encryption, Magnet/BitComet URIs, ... Remote control through a Web user interface Nearly identical to the regular UI, all in Ajax Advanced control over trackers, peers and torrents Torrents queueing and prioritizing Torrent content selection and prioritizing UPnP / NAT-PMP port forwarding support Available in ~25 languages (Unicode support) Torrent creation tool Advanced RSS support with download filters (inc. regex) Bandwidth scheduler IP Filtering (eMule and PeerGuardian compatible) IPv6 compliant Available on most platforms: Linux, Mac OS X, Windows, OS/2, FreeBSD qBittorrent 5.2.2 changelog: FEATURE: Use D-Bus to show file in file managers (Chocobo1) #24340 BUGFIX: Fix friendlyUnitCompact precision calculation (vafada) #24323 BUGFIX: Remove all top-level folders (glassez) #24333 BUGFIX: Use proper API for checking exit status (Chocobo1) #24349 BUGFIX: Delete stale lockfile when hostname mismatch (TurboTheTurtle, glassez) #24363 BUGFIX: Fix wrong removal procedure of watched folder paths (Chocobo1) #24413 BUGFIX: Don't reannounce before interface changes are applied (glassez) #24447 BUGFIX: Use Latin script for Bosnian locale name (Andy Ye) #24342 WEBUI: Fix performance of global checkbox toggling (tehcneko) #24316 WEBUI: Fix Safari transfer list header misalignment (Piccirello) #24377 WEBUI: Fix error when submitting magnet before metadata loads (Piccirello) #24378 WEBUI: Use correct row id when updating Rss Downloader feed selection (Chocobo1) #24402 WEBUI: Use SameSite=Lax for session cookie to fix cross-site login (Piccirello) #24422 WEBUI: Bring back properties panel expand/collapse button (vafada) #24430 WEBAPI: Only use X-Forwarded-Host header when reverse proxy support is enabled (Chocobo1) #24457 RSSS: Fix "RSS Smart Episode Filter" RegEx (nathanon-akk, glassez) #24398 RSS: Fix previously matched episode format (glassez) #24452 WINDOWS: Fix Python fallback search path (TurboTheTurtle) #24325 WINDOWS: NSIS: Allow to install x64 binary on ARM64 (Chocobo1) #24358 Download: qBittorrent 5.2.2 | 41.1 MB (Open Source) Download: qBittorrent 64-bit installer (qt6) | 43.6 MB Links: qBittorrent Home page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      Twozo Technologies earned a badge
      One Month Later
    • Week One Done
      Twozo Technologies earned a badge
      Week One Done
    • One Year In
      Twozo Technologies earned a badge
      One Year In
    • Veteran
      branfont went up a rank
      Veteran
    • Reacting Well
      Almohandis earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      497
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      126
    4. 4
      Steven P.
      85
    5. 5
      neufuse
      71
  • Tell a friend

    Love Neowin? Tell a friend!