16 Pixels

For Body Copy. Anything Less Is
A Costly Mistake

I know what you’re thinking. “Did he just say 16 pixels? For body copy? Obnoxiously big! 12 pixels is ideal for most websites.”

I’d like to persuade you otherwise.

As usability expert Oliver Reichenstein says in “The 100% Easy-2-Read Standard”:

[16 pixels] is not big. It’s the text size browsers display by default. It’s the text size browsers were intended to display… It looks big at first, but once you use it you quickly realize why all browser makers chose this as the default text size.

In this article, I’ll explain why 16 pixels should generally be the minimum size for body copy in modern Web design. If I don’t change your mind, perhaps you could chip in at the end and let me know why.

You see, in most cases, if you’re building websites with the font size set between 10 and 15 pixels, you are costing your clients money. And I aim to prove it.

Readership = Revenue

If you’re building a website for someone — even yourself — chances are its purpose is to make money.

Perhaps it’s to sell a product directly, or to offer a service, or just to generate leads. Whatever the case, it’s a business asset, and ultimately it has to generate a return on investment. It has to fulfill a revenue goal.

So, every element should be designed to achieve that goal. Including the copy. Especially the copy — because the copy is what convinces visitors to do whatever it is you want them to do on the website.

Think about it. If you don’t explain what people should do, or why they should do it, then they certainly won’t. And the only way to tell them is with text. And text means reading.

Important Facts About Reading

There are some particular findings that are pivotal to issues such as readership and readability and comprehension, which is really what body copy is all about. If people won’t read it, or if they can’t read it or understand it, then what’s the point of having it?

  1. At age 40, only half the light gets through to the retina as it did at age 20. For 60-year-olds, it’s just 20%.
  2. Nearly 9% of Americans are visually impaired, meaning their vision cannot be completely corrected with lenses.
  3. The distance at which we can read letters is a common measure of both legibility and reading speed. The greater the distance, the higher the overall legibility and comprehension are considered to be. The biggest factor that determines how far this distance can increase is font size. Seen any billboards lately?
  4. Most people, when sitting comfortably, are about 20 to 23 inches from their computer screens. In fact, 28 inches is the recommended distance, because this is where vergence is sufficiently low to avoid eye strain. This is much further than the distance at which we read printed text — most people do not hold magazines at arm’s length!
  5. 16-pixel text on a screen is about the same size as text printed in a book or magazine; this is accounting for reading distance. Because we read books pretty close — often only a few inches away — they are typically set at about 10 points. If you were to read them at arm’s length, you’d want at least 12 points, which is about the same size as 16 pixels on most screens:
    16-pixel text displayed on a 24-inch screen, next to 12-point text printed on paper.

    16-pixel text displayed on a 15.4-inch screen, next to 12-point text printed on paper.
  6. In a 2005 survey of Web design problems, bad fonts got nearly twice as many votes as the next contender, with two-thirds of voters complaining about small font sizes. If you think the situation has improved since then, think again. I randomly sampled some new blog designs on SiteInspire and found that the average font size for body copy was a measly 12 pixels. Some designs even used a minuscule 10 pixels. And none were over a weaksauce 14 pixels. Similarly, if you randomly sampled offerings on the popular Elegant Themes and ThemeForest, you’d find that every single theme sets the main content at just 12 or 13 pixels.

Fact: Most Web Users Hate The “Normal” Font Size

With this research in mind, let me ask: how many of your client’s readers are around 40? Because they have to work twice as hard to read as 20-year-olds. If they’re closer to 60, they have to work four times as hard.

Almost 1 in 10 of your readers also has trouble with their eyes. Of the rest who don’t, most will still have to strain to read text smaller than 16 pixels, even if they don’t notice that they’re doing it. (How often do you find yourself hunching over the screen?) And that’s if they’re leaning close, which they would likely find awkward and unergonomic. Their natural sitting position will be at least an arm’s length from the screen!

In short, for the average Web user, reading most websites is not unlike taking an eye exam.

The harder your text is to read, the less of it will get read — and the less of what is read will be understood. 10 pixels is essentially pointless. 12 pixels is still much too small for most readers. Even 15 pixels will turn off visitors who might have otherwise converted.

Thus, we can conclude that if you want the maximum number of people to read, understand and act on your text, then you need to set it at a minimum size of 16 pixels.

“But Users Can Zoom”

If you code it right, people with vision issues can always use the Option and + keys to enlarge the text.

Thus spake one Web designer in a discussion I had on this very issue.

Not so. The users who will most need to adjust their settings usually don’t know how. And the users who do… well, they’ll probably just take the easier path by hitting the “Back” button. It goes without saying that we shouldn’t take our clients’ money and then design websites for them that will make their visitors uncomfortable. Our personal tastes are not more important than best practices in usability.

Web design is not about what designers like. It is about what users want and what will best achieve our client’s goals.

If the objective of a client’s website is to achieve some revenue goal, then our role as designers is to come up with something to achieve that goal as effectively as possible. Picking a font size that we know most users will struggle to read, a font size that will reduce readership, a font size that will ultimately cost conversions, is not good choice.

In print, type as small as 8 points is an ideal compromise between readability and cost, because you have to pay for every millimeter you use. On the Web, you pay nothing for using more space — provided that readers find your copy compelling, of course. What you do pay for is readers finding your compelling copy so hard to read that they click away instead of converting.

So, the question is, are you prepared to cost your clients money for the sake of what looks good to you?

16 Pixels Is Not Big

Our tastes and aesthetic preferences as designers are a lot more malleable than we think. What “looks good” to us is largely the result of what we’ve seen other designers doing and what we’ve come to expect.

Unfortunately, most of the websites we’ve seen are packed with tiny copy, because once upon a time screens were tiny, and so designers matched them with tiny text — but no one got out of the habit.

This article is set in TeX Gyre Schola at 19 pixels. I picked this size because 16 to 18 pixels looked too small to me: as I sat back comfortably in my chair, 28 inches from the screen, I found myself squinting to see it. If I’d used Georgia or Verdana, 16 pixels probably would have been fine: they were designed with a larger x-height and so display better on screen.

Now, check out the footer just below and see whether you don’t hunch forward automatically, screw up your eyes and furrow your brow. That’s 12 pixels for ya. And if you still disagree after that, tell me why in the comments.

Bnonn and his daughter

Bnonn is the author of a series of free videos on creating websites that capture readers and turn them into customers. Known in the boroughs as the Information Highwayman, he helps people sell more online by improving their copy and design. When he’s not knee-deep in the guts of someone’s home page, he is teaching his kids about steampunk, Nathan Fillion, and how to grapple a zombie without getting bit.

  1. 301

    It’s a good rallying cry, but under the wrong flag I think.

    As designers we need to stop being such control freaks, and let the users define their own display.The most adaptive technique is using percentages, not points, and by no means pixels, especially in the world where every different device has different pixel (ppi) density.

    Do you remember the Dao of Web Design?
    http://www.alistapart.com/articles/dao/

    +14
  2. 302

    Ingrid Kast Fuller (@ingridfuller)

    November 29th, 2011 9:43 am

    The comments on this article are a perfect size for me. The article text is a little too big and the footer was too small.

    I agree with Petar Subotic, using percentages especially because we should be looking toward Responsive Web Design now because we have so many devices out today.

    +13
  3. 303

    Thanks, B. Nonn, for putting forward some interesting arguments.

    I have to disagree with the idea that there is no cost involved in using larger fonts on the web. Designing an effective and appealing web page is about the careful balancing of a number of different factors, with font size being just one. Get this *balance* wrong, and there could be a severe cost.

    For example, using a larger font would make a form look much longer, and research shows that this perception can be enough to reduce response rates. And it’s pretty clear to me that the lack of contrast between text and background on Mark Boulton’s site (for instance — nothing against him personally!) would undermine the readability more than the large font improves it.

    So while it’s great to have the data to suggest we over-estimate our readers’ ability to see what we produce, I think this should just be part of what we consider when deciding font size.

    Thanks,
    Jessica Enders
    Principal, Formulate Information Design

    +18
  4. 305

    There are so many things I take issue with here. One is that browsers’ default type being 16px means anything to a page design. How long have browsers been built that way? Why is 16px now the ideal body copy size as opposed to every other year they shipped this way?

    Not every site is a single column blog. You completely ignore the total design of the page (type hierarchy) in order to declare one size “best.” Your type is not well set enough to help your argument, either. Your line height makes this text *more* difficult to read than a smaller, well set size. The footnote bit is also set as #444 which makes it more difficult to read, but you’ve not written about contrast at all, only size.

    Further, you ignore mobile and focus on desktop only. How long will that be the prevalent browsing experience? Most of these devices are much closer to the eyes, and a properly set viewport clears up a lot of issues without going for 16px as a minimum.

    Lastly, you may think that just web designers read this. They’re not the only ones. So when I get a client who comes along and tells me every piece of text on the page must be at least 16px for a complex site, I’ll know where they got the idea. Should my H1 be 48px, too? I have had a client go back into a site design and restyle it for 16px minimum. It looks AWFUL. 16px type should not be a driving principle. Clear design thinking SHOULD be.

    +29
    • 306

      Until now every singles comments I’ve read is completely right, but @Rob you nailed it.

      Thanks for that!

      @Bnonn, though your intentions seems to be good, you clearly missed all of the design principles on this one…

      -4
  5. 307

    I stopped reading when it wasn’t fontsize=1 fontfamily=verdana and alien green text on black.

    What a newb. Eye damage is a right of passage and font-size = small a design crutch for the Y2K crowd.

    Honestly though, HE IS WRONG. How much money does Facebook make? What’s the font size there? Digestible, fast loading mini text.

    But why do 16px fonts when you can just have them scale perfectly to whatever device? And why not just use the zoom feature built into every modern device ever?

    Why do we constantly need to build entire sub industries around the ineptitude of the end user? If it’s just about money, well I say you’re losing money by changing web standards every 28 days like a menstrual cycle.

    CTRL + Mouse Wheel = Problem Solved. ALL CAPS 25px fonts and uninteresting content = money lost. If not because you alienated your viewer, then because you had to pay money to an adhoc blog writer.

    I say if you can’t read the internet you should be a Walmart door greeter until society changes again.

    I didn’t read to the bottom of the page where he tries to rebuke the web designer who said ‘use the golly darned zoom functionality’ … okay I did. But it wasn’t the massive text that got me there. Or the boring tone.

    If it’s really about making money, then why not just jack the lowest common denominator into the pseudo matrix and hook em up to a dopamine transmitter attached to a giant big arsed unmissable red button and charge money to their credit cards every time they push it and when they run out of FIAT credit supplied by a broken economic system replace said chemical with cyanide and turn their decomposing body into usable energy? How’s that for efficiency and a solution to the population problem.

    I would argue that it is far more costly in the long run to constantly cater to weakness and fight against evolution.

    RAISE UP humans. Try harder.

    And no, I didn’t hunch forward and furrow my brow to read the page footer but that is just because I have no interest in BNONN.

    Anyway, I jest… now that most people are using 1920×1200 monitors you really should up the font size. If you’re still using 1024 x 768 – get with the times. We live in a disposable society.

    Peace out.

    Thanks for letting me waste your time to add nothing to a needless conversation that common sense should have solved years ago. I hope you had to stare hunched over with furrowed brow getting massive screen radiation to read this 10pt facebook text.

    -53
    • 308

      Using a low contrast font to reduce readability of trolling comments is a usability problem. Here I sit trying to read it and straining my eyes in the process. Why not just hide the idiotic rant and make me click something to get a readable version?

      +3
  6. 309

    Funny thing – we always debate the ideal format for blogs and articles here (for ourselves and our clients). Our blog lacks readability and we’ve wanted to redesign it for 18 months now, we just never find the time! Hell, can’t even make the time to post blogs!! But, this is a design issue that we discuss for almost every site we create.

    Fundamentally though, the issues are:
    1) Too many words on a line is difficult for eyes to track – which leads to strain.
    2) Low contrast is difficult to read, which strains.
    3) Small font size is difficult to read, which strains causing squints, hunching, etc – and of course, also leads to #1.

    The fact is, while it looks large to us, the number of words per line is far closer to optimal – as opposed to 12, 15, or even 20 words in the worst cases. Part of the reason some college text books were so hard to read without falling asleep was the number of words per line. That and they were incredibly pointless and boring. However, in almost all printed material, you see pages broken into multi-column format. Why? It’s easier to read.

    And to keep the topic on track, this is about articles/blogs – copy intended for the user to read/consume. Forms are not included in this. However, the description of a form’s intent should be. (“Please fill out this handy contact form so we can send you a personalized design mug with accompanying vagrant sea bass!!”)

    Lotsa haters out here – but a good topic.

    Thanks,

    Greg of the OnWired clan.

    +12
  7. 310

    Very good article and an even better message. 16 px is a perfect on-screen size, and more importantly also means that text renders at a relatively legible size on phones & tablets, for sites which aren’t designed responsively or with a mobile-specific version.

    Although I have to agree with others who have said that we ought really to be steering away from px measurements in favour of % or em.

    +9
  8. 311

    Very constructive article. Content and content is the most important thing in all interfaces and of course the presentation it goes in paire with it. User friendly called by marketing people and I think that this rule have to be respected. Thanks again for this article. Daf

    0
  9. 312

    While I laud the premise that most web sites use too small text, 16px is just as wrong as 12px or 10px or 24px. Any px is wrong for sizing anything other than objects that have intrinsic sizes measured in px.

    Why?

    1-Screen densities vary widely, as do reading distance and other user environment variables. While the CSS spec defines a px as an angular measure that shouldn’t be affected by distance, in practice browsers don’t match up with the spec, because they’re incapable of anything other than too granular conformance – no fractions allowed – in matching up device px to CSS px.

    2-This is the bigger problem, and it’s huge: Defining font sizes in px (or pt or mm or any other “absolute” measure) disregards the browser default size, which disrespects the visitor. The browser default is presumptively the ideal size for the user. He’s the one in position to do anything about it if it’s inappropriate. No designer is. There’s too much variation in device densities, viewport dimensions, viewing distances, and viewer needs to ever say anything sized in px is ideal, or anything close thereto.

    If 16px is an ideal base size on your developing screen, and your developing browser default is 16px, then you’re also saying 1em is ideal. Indeed, 1em is always an ideal base size, as it (presumptively) matches the user’s ideal size perfectly, no matter the screen density, viewing distance, viewer, or any of the other environmental variables a designer has no knowledge of or control over.

    Zoom is a browser defense, like the “readable” scriptlet (which converts gray text to high-legibility black text and non-white backgrounds to high-legibility white here). Defenses generally aren’t necessary on sites that don’t present users with offensive styling.

    +5
  10. 313

    Peter McClory

    March 1st, 2012 7:12 pm

    I think you’re right about text generally being too small on most websites.

    There are of course a number of ways to do this, but in terms of the creative that gets signed off by the clients, I’m already moving towards larger font-sizes on all aspects of the designs, and I’ve only had positive feedback from clients.

    0
  11. 314

    It’s the principle of the thing. Increase body font size = improved reading experience (based on evidence given in this article, the web survey cited and opinions of many). Whether that means px or % or ems it doesn’t matter.
    If you’re into the responsive thing already than do it in ems or % or whatever, but I think the point is that body font size needs to be approx. 16px for all the good reasons explained in this article and most of the comments here.
    I have to agree with @Greg:
    “And to keep the topic on track, this is about articles/blogs – copy intended for the user to read/consume.”
    The topic is body copy text size, just like the title of the article says.
    Obviously caption text and sidebar text and meta text don’t need to be huge. If you start with 16px (or body {font-size: normal or 100%} and then whatever that ends up being using relative measurements) you can apply same typography principles of hierarchy ect. I think of this as just moving up the scale.

    Check out trentwalton.com specifically. One of my favorite sites for many reasons, but the typography is one of them. The body text font size is 20px (or 137.5% for screens larger than 900px wide) Another good example of a nice looking site with great typography is jasonsantamaria.com his font size there is 20px.

    +1
  12. 315

    The font in this article hurts my eyes (actually makes me feel a bit sick) and is definitely not optimum.

    +2
  13. 316

    While I totally agree that overthinking the common use of 12 or 13 px big fonts is necessary and 16px is indeed a good option.

    I think the argument “… all browser makers chose this as the default text size” shouldn’t matter. Just because something is the default, it does not mean it is the best option.
    There are far better arguments for increasing font size and they make much more sense than using “default”.

    0
  14. 317

    I learned a lot from the article and comments. I especially appreciated learning that em or % is probably the better way to go for setting on-screen font size. Thank you, all.

    -2
  15. 318

    I have an approx. 18 in. monitor, which (I just measured) I sit 18 to 20 in. from. At a 1600 by 1200 resolution, this leads to a DPI of a little over 100. While I can’t be sure my vision counts as normal (I’m thirty and have awful sight without correction. With an up-to-date prescription can be corrected to better than 20/20, but my current prescription is a few years old.), but I have to view much of the web at various levels of zoom. In particular, I have to zoom (oft mentioned above) Facebook quite a bit.
    Luckily Chrome remembers my zoom settings for various sites. Otherwise I’d probably go batty. It’s like a ritual, go to new site, fix font size, read content.
    Doing a little math, 12px text at 100 dpi is less than 9pt text. At a reading distance nearly one and a half times what is considered normal for printed matter where 9pt text is acceptable. Furthermore, due to the low DPI of most displays (relative to printed material at 300-600 DPI), typeface details at small sizes are less clear than print as well.
    The article’s recommended 16px text is nearly 12pt and the 19px it’s set in is a little over 13.5pt. While these may seem like large sizes, when one factors in the reading distance, the angular measurements are equivalent to 7.68pt and 9.12pt respectively, while 12px is reduced to an unreadable 5.76pt.

    +7
  16. 319

    “Fact: Most Web Users Hate The “Normal” Font Size”

    How should we understand that heading? The text says the opposite.

    0
  17. 320

    your blog looks fine in 16 point but my boss can read it 10 miles away. Its too big and isnt practical for web design in general.

    Let the user decide.

    0
  18. 321

    Honestly, attempting to read this article with body copy so large made my head hurt, and the shadow on the drop caps made things worse. I’m sorry but I actually find the font choices and styling in this article overall to be awful (my opinion).

    I was intrigued because I normally use 13px (which I’m pretty sure I learned from a smashing article a few years back), and some of my clients (mainly the ones who attempt to design themselves and are the worst to deal with) comment that it’s small.

    So I went into this hoping to learn something new… I learned not to use 16px for body copy. Never would I want to put my users through that, outside of a welcome paragraph at the top of the page.

    -1
  19. 322

    I am designing my website. I am trying to find out the best size for the texts. You are 100% correct. If my visitors are in trouble to read the texts, then why should I write the texts?
    Thanks for your excellent arguments and working samples.
    With best of regards,
    Subodh

    0
  20. 323

    Ezekiel (@ebinion)

    August 17th, 2012 12:42 am

    A blanket size of 16 pixels for body copy is wrong for many reasons. However, it’s clear that 12px is too small and as interactive designers we should trend upwards in our fonts sizes.

    A few more good reasons to increase font sizes:

    1. Larger text is easier to read at a glance. This is especially great for the segment of mobile users that truly have “one-eye and one-hand” during use.

    2. TVs are emerging as a web platform. Users sit much further away from them, making it difficult to read smaller fonts.

    3. Tools like Instapaper & Reader make money (in-part) by giving users an experience that’s easier to read than the websites that we’ve been designing for years. (Take a look at their font sizes.)

    0
  21. 324

    12-14 seems to be my comfort level, I would opt on larger vs small. Facebook is too small.

    Most of my clients prefer larger vs the small. (Maybe we are old).

    I am having difficulty with the contrasts. Many of the templates I see are low contrast (light to medium grey on white) – I have big problems with this.

    +1
  22. 325

    I’m calling bullshit!
    Here’s another UE guy trying to claim fame and fortune and industry authority.
    The larger the font the harder it is to skim the page, because your has to do more work and and it also makes the page longer and that just adds to the scroll time. computers are going to retina as well and in a few years the monitor definition and clarity will be that much better. Not a point for now but just saying.
    I’m going to listen to a guy who is wearing glasses and obviously biased.
    I’m calling bullshit.

    0
  23. 326

    I never realized that designers were such a conservative lot! Okay. I knew they were politically speaking (though they don’t like to think of themselves as conservatives, most are neoliberals or libertarians, so vote for Clinton-like Dems). BUT I figured that, surely, designers are open-minded when it comes to design itself, and — since they are designers creating user interfaces, and not artists — I figured that surely designers want to maximize user access and, well, usability. Guess I was wrong about that. These comments mostly demonstrate a stunning degree of dogmatism. Nearly every comment defended the common practice of setting web type at 12px or so. Most of those comments gave no reason at all except “design” (ie: it’s what the designer is used to doing, and used to seeing).

    Unfortunately though, the author of this article did himself, and his case, a *tremendous* disservice by choosing to set the article’s type at 19px. And he doesn’t explain this until late in the article, so I suspect most readers assume the article is set at 16px. (It also makes the examples of smaller type look extra-small, which is a bit deceiving, albeit unintentionally so. I think.)

    Moreover, while the author goes on about the importance of considering the diversity of users, and how users actually view webpages, the author opts for a rather obscure font to lead his font stack — and it’s his view of that particular font which leads him to set his type at 19px. He explains that he probably would have used 16px in the article had he chosen Georgia or Verdana. Well, I the article is set with Georgia on my PC, and I suspect that’s what many readers see. And Georgia at 19px really truly does look oversized. The author failed to take his own advice when he did not choose Georgia, or another very common font, to lead his font stack (or choose to use a hosted web font service which would guarantee we would see the same font). This really puzzles me because then the author, by his own admission, would have stuck with 16px had he used Georgia or another font with a very large x-height.

    (Btw, I suspect the history of web designers having to use Georgia and Verdana is what led most to reduce the default p font size to something like 12px or maybe 14px. The most recent web font releases from Microsoft — the distributor of Georgia and Verdana too — don’t look overly large at all at 16px. Constantia and Cambria look fine, or even a tad small, at 16px …or 1.0em.)

    Steve

    +3
    • 327

      This comment (from Steve) absolutely nails it. I too saw the article at 19px and thought I was looking at 16px until halfway through the article. I didn’t dislike the article font at all, but it was a tad larger than necessary – ironically, 16px would likely have been perfect on my display.

      That said, I want to echo the call for a truly device-independent size unit (which points would be if browsers didn’t asininely assume 96 DPI) and, absent that, deriving all sizes as percentages from the browser’s configured default – such that the body of the text on the site is 100%. What really needs to happen is for browsers to make it super-easy (and obvious) to set the “base” font and size.

      Also, for what it’s worth, the size of the font in this comment-entry textbox is an ungodly 10.68 px. I can’t read it without straining. At least the comments themselves are OK.

      0
  24. 328

    I agree 100% with your article. But I still had IE on 125% zoom so I could read the other comments. Anyone who disgrees with you is either an idiot, young,or a webdesigner (minor shades of difference.

    +2

  1. 1

    I’m not sure if it’s on purpose or not, maybe I’m missing something…

    BUT

    I find it hard to take the article seroiusly (even though I agree with the point being made) due to the styling used throughout;

    The Red Impact headers and the drop shadow & spacing on the first letter of the new paragraph. It’s horrible.

    I was also under the impression that Sans-serif font’s are easier to read on screen than serif fonts, so on an article about legibility, why choose a serif font (no matter the size?).

    Maybe it’s ironic? Maybe I’m dumb? Maybe I just missed an inside joke?

    +50
  2. 2

    There are so many things I take issue with here. One is that browsers’ default type being 16px means anything to a page design. How long have browsers been built that way? Why is 16px now the ideal body copy size as opposed to every other year they shipped this way?

    Not every site is a single column blog. You completely ignore the total design of the page (type hierarchy) in order to declare one size “best.” Your type is not well set enough to help your argument, either. Your line height makes this text *more* difficult to read than a smaller, well set size. The footnote bit is also set as #444 which makes it more difficult to read, but you’ve not written about contrast at all, only size.

    Further, you ignore mobile and focus on desktop only. How long will that be the prevalent browsing experience? Most of these devices are much closer to the eyes, and a properly set viewport clears up a lot of issues without going for 16px as a minimum.

    Lastly, you may think that just web designers read this. They’re not the only ones. So when I get a client who comes along and tells me every piece of text on the page must be at least 16px for a complex site, I’ll know where they got the idea. Should my H1 be 48px, too? I have had a client go back into a site design and restyle it for 16px minimum. It looks AWFUL. 16px type should not be a driving principle. Clear design thinking SHOULD be.

    +29
  3. 3

    For people like me who never read what Oliver Reichenstein essentially wrote 5 years ago.

    +18
  4. 4

    Thanks, B. Nonn, for putting forward some interesting arguments.

    I have to disagree with the idea that there is no cost involved in using larger fonts on the web. Designing an effective and appealing web page is about the careful balancing of a number of different factors, with font size being just one. Get this *balance* wrong, and there could be a severe cost.

    For example, using a larger font would make a form look much longer, and research shows that this perception can be enough to reduce response rates. And it’s pretty clear to me that the lack of contrast between text and background on Mark Boulton’s site (for instance — nothing against him personally!) would undermine the readability more than the large font improves it.

    So while it’s great to have the data to suggest we over-estimate our readers’ ability to see what we produce, I think this should just be part of what we consider when deciding font size.

    Thanks,
    Jessica Enders
    Principal, Formulate Information Design

    +18
  5. 5

    I find this article hard to take seriously.

    Font size should be determined by the nature of the site and the target audience.

    To say 16 pixels should be the minimum for all sites is a blinkered view.

    +17
  6. 6

    Hey, Kyle. Problem is, this post is actually set in 19px. A lot of people missed that in the article – which proves they were skimming, and prob coz it was hard reading.

    So, the font was too big. And that’s why it was hard work to read. At 16px it’s much more readable.

    I don’t understand how or why on earth he’d try to argue for 16px then not even use it! Totally undermined the credibility of his arguments. (Especially when he says “See how small 12px looks now. Well of effing course it looks small against **19px**!!)

    +15
  7. 7

    My tests indicated younger viewers (< ~30) are less likely to read larger web copy. My guess to the reason was everything blends together and more scrolling is required.

    Personally, I've always found large text to look like an old school ebook sales page.

    +14
  8. 8

    It’s a good rallying cry, but under the wrong flag I think.

    As designers we need to stop being such control freaks, and let the users define their own display.The most adaptive technique is using percentages, not points, and by no means pixels, especially in the world where every different device has different pixel (ppi) density.

    Do you remember the Dao of Web Design?
    http://www.alistapart.com/articles/dao/

    +14
  9. 9

    16px != 16pt. 16px == 12pt.

    +13
  10. 10

    >I find it hard to take the article seroiusly (even though I agree with the point being made) due to the styling used throughout;

    Are you joking? He presents usability studies and examples, and you dismiss it because you don’t like the fonts he chose? *sigh* You’re not doing much to combat the combat the stereotype of the myopic, superficial designer. This is exactly the attitude an article like this is meant to combat; there’s more to usability than your personal opinion!

    +13
  11. 11

    Ingrid Kast Fuller (@ingridfuller)

    November 29th, 2011 9:43 am

    The comments on this article are a perfect size for me. The article text is a little too big and the footer was too small.

    I agree with Petar Subotic, using percentages especially because we should be looking toward Responsive Web Design now because we have so many devices out today.

    +13
  12. 12

    Richard Williams

    October 7th, 2011 6:22 am

    It is a good point, but I still don’t think a large font is suited to long pieces of text.

    When I got to the small text at the bottom I found it a relief to not have to move my eyes so far/quickly. I’m slower reading the large font.

    +12
  13. 13

    Funny thing – we always debate the ideal format for blogs and articles here (for ourselves and our clients). Our blog lacks readability and we’ve wanted to redesign it for 18 months now, we just never find the time! Hell, can’t even make the time to post blogs!! But, this is a design issue that we discuss for almost every site we create.

    Fundamentally though, the issues are:
    1) Too many words on a line is difficult for eyes to track – which leads to strain.
    2) Low contrast is difficult to read, which strains.
    3) Small font size is difficult to read, which strains causing squints, hunching, etc – and of course, also leads to #1.

    The fact is, while it looks large to us, the number of words per line is far closer to optimal – as opposed to 12, 15, or even 20 words in the worst cases. Part of the reason some college text books were so hard to read without falling asleep was the number of words per line. That and they were incredibly pointless and boring. However, in almost all printed material, you see pages broken into multi-column format. Why? It’s easier to read.

    And to keep the topic on track, this is about articles/blogs – copy intended for the user to read/consume. Forms are not included in this. However, the description of a form’s intent should be. (“Please fill out this handy contact form so we can send you a personalized design mug with accompanying vagrant sea bass!!”)

    Lotsa haters out here – but a good topic.

    Thanks,

    Greg of the OnWired clan.

    +12
  14. 14

    You make a good point. I’ll try that on the new website I’m working on.

    +11
  15. 15

    It’s not that I don’t like the chosen fonts, it’s that I think they adversely affect the legibility of the article.

    I’m using Firefox 7.1 (I’ve noticed in Chrome the font’s pulled in by the browser are different)

    Take for example the “But Users can Zoom” section.

    The styled “T” at the start of “Thus spake one Web desiginer…” the large red lettter and large grey drop shadow touches the “h” from thus. I find that difficult to read.

    The article is about making text easier to read… The next paragraph starting ‘Not so.” Is unstyled. I find it much easier to read.

    That was only my point. Not that it’s ugly – just it’s harder to read in that style.

    There are further comments below stating my thoughts on serif vs sans-serif for screen use are incorrect. I accept this and as mentioned would appreciate any links to research on these to read up on.

    +11
  16. 16

    Niels Matthijs

    October 7th, 2011 3:23 am

    Very (very) tiring article to read. Short reading lines + big font sizes don’t allow people to sit down and read the text comfortably. You know what doesn’t happen in books … scrolling and readjusting to your eyes to find the reading line again. Which I need to do like every 20 seconds when reading this article.

    Doesn’t help that the site is completely in shambles on FF7 (really??)

    +10
  17. 17

    Hey Scott, I know what you mean about the headers. The drop shadow is encroaching into the text and that does affect readability. I also understand where the others are coming from. I’m just writing to say I thought you handled all this well and the fact that you wrote back and requested documents to read further shows you love what you do and you have respect for the site in general.

    Cheers,

    +10
  18. 18

    Hi,

    I strongly disagree. You simply cannot generalise in such a manner. You should setup personas and test cases based on your target and current markets, if your set of personas does not (and will intentionally) contain anyone over the age of 28 why should your design consider that user secondary?

    Luckily I read this article in an RSS feed reader where I can choose my preferred font. after reading that you had intentionally styled your article in TeX Gyre Schola at 19 pixels I thought I would look at the article in its original format.

    The serif font strong colours and large font gives a childish impression and so it is much harder to take the article seriously.

    Additionally perhaps your lower contrast colour (#444) and hard to read serif font required you to select greater than 16px. Try #000 and a sans-serif font and I suspect that 14-15px will appear a lot more serious and having done so in both a feed reader and this webpage I can assure you it is definitely more readable.

    There are far more complex factors at work than just size and lack of structure in body copy is far more important than larger font sizes in improved readability. You are correct in identifying that font sizes are often too small for specific user segments, however, generalising to the extent that you do is a step too far. Fonts and users are veried and the appropriate design decision is a complex mix of this.

    PS your main heading is highly unreadable, if you changed it from its current:

    48px font size, 40px line height and centre alignment

    to

    14px sans-serif, 18px line height and left alignment

    it would be much easier to read for the majority of users…having overlapping line heights and center alignment is very poor for readability…

    +10
  19. 19

    I think you point at something interesting. The large font make us read it slower and the smaller to just go trough it and not really read it. To enlarge the font was a tip I got years ago when it comes to proofreading as it is to easy to just “skim” it when the text is small.

    +10
  20. 20

    Phil Middlemass

    October 7th, 2011 5:28 am

    With the variation in screen resolutions these day I find it hard to that this kind of research on board.

    Lets look at it like this:

    I have a laptop at home, 15.6″ display running at 1920×1080 = a pixel density of 141ppi

    My wife has a laptop, again 15.6″ display but at 1366×768 = pixel density of 100ppi

    So assuming the default dpi is set in the OS on both machines, my wife’s laptop will display browser text 40% larger than on my own laptop simply down to the resolution.

    Resolution = massive factor in readability for text on screen

    These kinds of articles can only be taken as a guidance, there are too many factors to consider to come to a single conclusion that can apply to all

    16px on my laptop looks OK, bigger than I’m used to, but on my wife’s machine is actually difficult to read, it is all subjective, everyone has a different comfortable reading size because of their respective screen sizes and resolution.

    +9
  21. 21

    What? No, this is not what you should be teaching people. The standard size for font on a browser is 12pt, not 16px. Points are measured in physical units, which means that as pixel density increases, the displayed size will be the same.

    Pixel density used to be lower, which is why everyone uses 12px as their font size. Because when monitors displayed around 72dpi, 12pt, was 12px. Now monitors display around 96dpi, and guess what, 12px * (96/72) = 12px * (4/3) = 16px. Ignorant web designers who did not take the time to understand the difference between points and pixels assumed they were the same because coincidentally, at 72dpi they are the same.

    What you are encouraging people to do is not a solution. It’s the same problem that caused this, which is using a digital unit of measurement instead of a physical one. Once monitors inevitably improve and pixel density increases this problem will be the same again. Also, 16px fonts will look huge on old monitors. 12pt fonts will look the right size forever.

    P.S. Since computer dpi standards aren’t concretely set, the actual physical sizes will vary in practice. 72dpi, and 96dpi are just average approximations that are convenient to use for monitors in those ranges, but the principle still holds, even though it’s not exact.

    +9
  22. 22

    I think in theory it’s a great idea, and would be great for certain situations, but I think to generalise would be a mistake and there’s much more to consider than just the size of font when you’re a designer.

    We don’t tend to plonk a large amount of text and leave it, we use other devices to make it easier to read such as segmenting, highlighting, making keypoints larger etc. In this page the font has proved to be easier to read I agree but wouldn’t work always.

    We don’t often get briefs that just feature the need to have as much text as a book would.

    I’m not disagreeing entirely, I just think the examples used in this piece are slightly biased, and don’t show the situations where it would make websites harder to use. It depends entirely on the website and this idea would be great for things like blogs but would make it especially hard to layout e-commerce and catalogue sites in a user friendly way and still get vital information in without the need to scroll constantly.

    Also a key thing is having easy to use navigation. With increased font sizes as standard your side navigation would constantly be falling onto 2 or three lines which would throw up lots of usability issues.

    +9
  23. 23

    Martin, I am glad that you are pursuing a degree in web development. I am a (young) college professor teaching web design and development, I can say that the number one issue beginning students have when designing web pages is making the font size too big. The article about using 16 pt/px font has some validity, but as with anything in design, there is no rule. Saying that you always have to use 12px is wrong, but saying that you always use bigger fonts could also be wrong. There are too many factors that go into any type of design to say that you should always use *this* for *that*.

    Good luck with your degree!

    +9
  24. 24

    Very good article and an even better message. 16 px is a perfect on-screen size, and more importantly also means that text renders at a relatively legible size on phones & tablets, for sites which aren’t designed responsively or with a mobile-specific version.

    Although I have to agree with others who have said that we ought really to be steering away from px measurements in favour of % or em.

    +9
  25. 25

    Interesting.

    Yet what font-size does Smashing Magazine use on their own site… ?

    :)

    +8
  26. 26

    Cameron Chapman

    October 7th, 2011 4:15 am

    Personally, I think line height and contrast are equally important to type size when it comes to readability. My personal favorite is to start with a text height of 14px and a line height of 24px. Depending on the particular font, I might go up or down from there. But having a line height that’s roughly 1.7x the font size does way more for readability than font size alone.

    +8
  27. 27

    Interesting points, it was definitely very easy to read this article.

    +8
  28. 28

    The first thing I did to read this was reduced the font size down to something around 12 point, then when I got to the comments I bumped the size back up sot that the comments are readable. I think 16 is a bit much, but a 14 or 15 might be an acceptable compromise. As pointed out in the article those that like a smaller font can probably more easily figure out how to reduce display size than those that prefer a larger font. I can’t help but wonder though that for those who override website settings to display fonts much larger than normal if when viewing a page like this they don’t get slapped in the face with 30 point fonts or something similar.

    +8
  29. 29

    Justin Heideman

    October 7th, 2011 9:45 am

    I’m no fan of small fonts, but this article is merely the author’s opinion that less than 16px is costing you money. There is no data to back this up. There is some ancillary data, suggesting that users don’t like small fonts, but that doesn’t correlate into lost revenue. Unless the author can cite a specific A/B test that shows decreased revenue, this article is not very accurate.

    Again, I agree that small fonts are often bad. I just don’t think it’s as cut and dry as the author states. There’s more to readability than font-size. One must consider the face, line spacing, use of ligatures, etc. Size is merely one tool in the typographer’s toolbox.

    +7
  30. 30

    Just the opposite – the larger font IS more suited to long text. How old are you? (as the article asks) – I actually found the body text of the article easier to scan/read than the smaller text below. AND, his points are valid – I’m so tired of needing to zoom in order to read simple text on web sites (especially some web development sites); AND, the web is becoming so full with alternate sources of information that you CAN read – I’ve just given up on making the attempt. I have found myself completely bailing on 4 or 5 sites a week when I’m confronted with small text. Much more cost effective of my time to scroll down the Google list to a new site.

    +7

Leave a Comment

Yay! You've decided to leave a comment. That's fantastic! Please keep in mind that comments are moderated and rel="nofollow" is in use. So, please do not use a spammy keyword or a domain as your name, or it will be deleted. Let's have a personal and meaningful conversation instead. Thanks for dropping by!

↑ Back to top