Developers · problem and fix
Why is it hard to read long research papers? Causes and fixes for Mac users
Long research papers are hard to read because they pack dense arguments, unfamiliar terms and figures into text you often read under time pressure. Most people start on page one and read straight through, which is the slowest way to find what they need. The fix starts before you open the file.

The short answer
- Long papers are dense, full of unfamiliar terms, and built around an argument you must hold in memory.
- Researchers read about 22 papers a month in 2012, and just over half of them on screen.
- Print beat screens for comprehension in a 54-study meta-analysis, and the gap grew under time pressure.
- Decide your question first, read in passes, and keep annotations in a format your app can open again.
- Lazur can explain a term or point at a figure while you read. It does not read the paper for you.
What reading long research papers costs you
Hours you spend on reading
The Tenopir survey found researchers read about 22 papers a month in 2012, down from 27 in 2005. At just over 30 minutes each, that is roughly 11 hours a month. The data is old and covers US scholars only, so treat it as a rough benchmark, not a measure of your week.
Comprehension lost on screens
The Delgado et al. meta-analysis reports an average effect of g = -0.21 favoring paper for comprehension. The effect was larger under time pressure and for explanatory text, which is the kind of writing a research paper is. Effects near 0.2 are usually called small, so expect a modest penalty, not a failure.
Weekly hours on documents
In a sponsored Iris.ai survey of 500 corporate research professionals, 69% spend at least 3 hours a week reviewing documents. Another 19% spend over 5 hours a week reading to keep up. The study is sponsored by an AI vendor and gives no year, so use it as a signal only.
Money and grades: no reliable figure
I found no reliable figure for what reading load costs in money or grades. Any number you see for that should come with a named, checkable source. Your own cost is easy to estimate. Count the papers you read in a week and multiply by the minutes each one takes.
Why it happens
Papers are written for specialists
Research papers assume you know the field's terms, its methods and what counts as a result. When a term is missing, you stop, look it up and lose the thread. The paper never pauses to explain itself, so every gap falls on you.
Screen reading carries a small penalty
The meta-analyses I could verify show a small average penalty for screens. Clinton (2019) reports g = -0.25 for screen reading of explanatory text, with no difference in reading time. The penalty touched literal recall and the ability to reproduce inferences.
Time pressure makes the gap bigger
Delgado et al. found readers do better on paper when reading time is limited. A deadline pushes you to skim a dense paper. Skimming is the situation where the paper advantage grew largest, so the deadline hurts most.
Your file setup adds friction
Annotations split across apps are easy to lose. Zotero's built-in reader stores highlights in its database, so Preview will not show them unless you export a PDF with embedded annotations. Each time you switch tools, you reread what you already marked.
Too many papers, too few filters
Once you have forty open tabs and a folder of PDFs, every paper competes for the same hour. Without a triage step, you start reading the wrong papers in full. The weekly-hours figures above show how much document review fills a normal week, even in a sponsored survey.
How to fix it
These work with or without any app.
Write one question before you open the PDF
Write one sentence: what do I need from this paper? It might be a method, a number or a claim you plan to cite. Keep the sentence visible. This one step turns a long paper into a search with a target, so you stop reading every section with equal care.
Read in three passes
Pass one is a 10-minute scan. Pass two is a focused read of the introduction and results. Pass three covers only the parts that answer your question. This is my suggested routine. The research I checked did not test it, so judge it on your own papers.
Print the hardest sections
The paper advantage is the one reading finding I could verify across many studies. For a dense methods section or a theory-heavy discussion, print those pages. Keep the rest on screen. Test whether this helps you before you rely on it.
Use a time box near the survey average
The 2012 survey average was just over 30 minutes per article. Set a timer for 30 minutes. When it rings, write your five-line summary, then decide whether to keep going. A timer stops you from rereading one paragraph for an hour.
Keep notes in one place
Pick one home for notes, such as one Apple Notes file or one Zotero note per paper. In Preview, use File > Export to PDF to keep annotations editable. Hold off on File > Print > Save as PDF until your notes are final, because that path makes them permanent.
Group your open papers in Chrome
Right-click a tab and add it to a group named for the project. Close the groups you are not using. Fewer open tabs means fewer half-read papers waiting on you, and fewer tabs to hunt through when you need a citation.
Ask Lazur for the term, then check the source
Hold ⌥ ⌘ and ask what the term means in this paragraph. Lazur answers out loud from what is on your screen. Then find the authors' own definition in the paper and write that down, not the spoken answer.
Most of the difficulty is not you. A long paper asks for sustained attention on dense text, unfamiliar terms and figures that depend on the text around them. You also tend to read it in the worst conditions, with a deadline, forty open tabs and a question you have not written down yet.
How many papers do researchers read each month?
The most-cited numbers come from a survey led by Carol Tenopir at the University of Tennessee. It drew about 800 scholars, all based in the US. In 2012, respondents read an average of 22 papers a month, about 264 a year. In 2005 they read 27 a month. That was the first drop since the survey began in 1977.
22 a month
Papers the average researcher read per month in 2012, down from 27 in 2005
The Scientist: Researchers Read Fewer PapersJust over half
Share of papers read on screen in 2012, up from about one fifth in 2005
The Scientist: Researchers Read Fewer Papers69%
Of 500 corporate research professionals spend at least 3 hours a week reviewing documents (sponsored survey)
Scientific Computing: Study shows 66% of researchers overwhelmed by volume of published research-0.21
Comprehension effect favoring paper over screens across 54 studies (Delgado et al., 2018)
TUM Center for Educational Technologies: Don't throw away your printed booksTime per paper is the other half of the picture. Respondents spent just over 30 minutes on each article in 2012. The Scientist calls that the shortest average in the survey's history. Scientific American's account gives 32 minutes for 2005 and just over half an hour for 2012.
Multiply the two numbers and the picture gets clearer. Twenty-two papers at just over 30 minutes each comes to roughly 11 hours a month. That is a real slice of any month, and it comes before you write, run an experiment or answer email.
Treat these numbers as a snapshot, not a current measure. The Tenopir data is from 2012 and covers US scholars only. A sponsored Iris.ai survey of 500 corporate research professionals adds a newer angle. It found 69% spend at least 3 hours a week reviewing documents, including journal articles, conference papers and reports. The study is sponsored by an AI vendor, so read that figure with care.
Why is it hard to read long research papers in the first place?
Length is not the only factor. A short article usually makes one case and stops. A research paper stacks a question, a method, results and a discussion. Each part depends on the one before. If you lose a definition on page two, the results on page nine can stop making sense.
- Dense vocabulary. Field terms and abbreviations repeat, and you may not know half of them.
- Methods written for specialists. Procedures are listed in exact detail, which is slow to scan.
- Figures that need the text. A chart often answers a question the paragraph raises, so you flip back and forth.
- No clear question. Without one, every paragraph looks equally important.
- Long sentences with nested clauses. Each one asks you to hold the subject in memory until the verb arrives.

Does screen reading make research papers harder to understand?
The best evidence I could verify is a 2018 meta-analysis by Delgado and colleagues, summarized by the TUM Center for Educational Technologies. It covered 54 studies and more than 170,000 participants from 2000 to 2017. Print came out ahead for comprehension, with an effect of g = -0.21 favoring paper. The summary page does not report a confidence interval.
The advantage was not even across texts. It was larger for expository writing, which explains and argues, than for narrative writing. Readers also did better on paper when reading time was limited. A research paper is expository and often read under time pressure, so the finding fits your situation more than a novel would.
Clinton (2019), also summarized by TUM, reports g = -0.25 for screen reading. The effect was concentrated on explanatory texts and affected literal recall and the ability to reproduce inferences. Reading time did not differ between media, so paper was also the more efficient option in that study.
How to read a long academic paper in one hour
Say you have one 14 page paper and one hour. This is a hypothetical example, not a measured case. Spend the first 10 minutes on the title, the abstract, the end of the introduction, the figures and the conclusion. Write one sentence that says what the paper claims. Then decide whether you need the whole thing.
Use the next 25 minutes on the sections that answer your question. If you are checking a method, read the methods. If you are deciding whether to cite the paper, read the results and the limitations. Leave the rest. Mark a short note in the margin each time something surprises you.
Spend the last 15 minutes writing a five-line summary in your own words. Include the claim, the evidence, one doubt and the question you still have. If you cannot write those lines, you have not finished the paper, whatever the clock says.

Mistakes people make when they read a long paper
- Starting on page one and reading straight through. Papers rarely reward linear reading when you have a specific question.
- Highlighting everything. A page full of yellow tells you nothing about what mattered.
- Stopping at every unfamiliar term. Mark it, keep going, and come back once the paragraph makes sense.
- Reading the equations before you know their goal. Work out what the equation is for first.
- Keeping forty tabs open. You lose track of which paper was which, so you reread them.
- Trusting one summary, from a person or an AI tool, without checking the paper's own wording.
Highlighting is the habit that costs the most time. Each highlighted line gets read twice, once when you mark it and again when you look for it later. Notes that say why a line matters are worth more than the color.
A three-pass reading routine you can try this week
This routine is a suggestion, not a tested method. The research I could check did not confirm specific reading fixes. Treat it as an experiment. Run it on one paper, then keep it or change it.
Pass one takes about 10 minutes. Read the title, abstract, section headings, figures and conclusion. Ask what the paper claims and whether that matches your question. If the answer is no, stop here and file the paper.
Pass two takes about 30 minutes. Read the introduction and the results closely. Write down each term you do not know and look it up before the next section. Keep one running list of questions in a single note, not scattered across the margins.
Pass three is for the parts that matter. Read the methods only if you need to judge the evidence. Check whether the limitations match the strength of the claims. Then write your five-line summary and save it with the paper, so you can find both later.
Set up your Mac so your paper notes survive
Preview is already on your Mac. Open the PDF, click Show Markup Toolbar if you cannot see it, and use highlight, notes and shapes. Apple's guide also covers sketch, signing and form filling. Use File > Export to PDF to keep annotations editable.
Avoid File > Print > Save as PDF until your notes are final. Apple's guide says that path makes annotations permanent and uneditable. Save an editable copy first, then make a flattened version only when you need one for sharing.
If you use Zotero, its built-in reader saves highlights and notes in Zotero's database. An external reader such as Preview will not show them unless you export a PDF with embedded annotations. Zotero's support page also warns that adding, deleting, reordering or rotating pages in an external reader can misplace annotations.
Skim is another PDF reader for the Mac. Its SourceForge release folder lists 1.7.19 as the newest version, dated 2026-11-04. The official site did not load for me, so check the release page yourself before you download anything.
Where Lazur fits in your reading routine
Lazur is a voice assistant for the Mac. You hold ⌥ ⌘, ask about anything on screen, and it answers out loud. For a paper, that means you can ask what a term means while the sentence is still on the screen. It works in any app that shows the text, including Preview and Chrome.
Ask where something is, and Lazur draws a circle and a label around it. That helps when you want the sample size or a figure legend and do not want to hunt. Ask how to do something, such as turning on the markup toolbar, and Lazur guides you one click at a time. It waits for each click. You still do the clicking.
Lazur does not read the paper for you. It does not edit your PDF or click through apps. Check any definition against the paper's own text before you cite it or repeat it. I did not find a published test of how accurately it reads technical papers, so try it on papers you already know first.
Questions to ask Lazur while you read a paper
- Hold ⌥ ⌘ and ask what this term means in this paragraph.
- Ask where the sample size is reported on this page.
- Ask what the axes of this figure measure, then check the caption yourself.
- Ask Lazur to research two other papers on the same method and report back.
- Hold fn and dictate your five-line summary at the cursor, in whatever app you use for notes.
Dictation suits the summary step. Hold fn and talk. The text lands at your cursor in any app. Speaking the summary also forces you to say the point in plain words, which is a useful test of whether you understood it.
Privacy and data rules for unpublished research
Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to produce an answer, and they are not stored. Content is never used to train AI models. Check Lazur's privacy terms before you rely on those points for sensitive work.
Research papers often include unpublished data, patient information, or details your employer or ethics board controls. Follow those rules before you paste or speak any of that material into an AI tool. If you are unsure, remove the sensitive parts or ask the data owner first.
Pick one paper and time it this week
Pick one paper you must read this week. Set a timer for 30 minutes, close to the survey average, and run the three passes. Write your five-line summary. Note how long it took and how many times you reread a section. Then decide whether the routine helped.
Pricing is simple to check. Lazur has a 3-day Pro trial with no credit card, and it starts when you first open the app. Pro is $18 a month, or $15 a month billed annually, with 150 AI actions. Dictation is unlimited on both plans. You can download Lazur or compare plans on the pricing page.
If your reading lives in the browser, the browser setup matters as much as the paper. For tab groups, shortcuts and a researcher's daily setup, read Chrome for researchers on Mac in 2026. Keep the number of open papers small, and close the ones you have finished.

Faster with Lazur
Where Lazur helps with reading long research papers
Hold ⌥ ⌘ and say what you want. Lazur sees your Chrome window. Lazur looks at your screen and answers out loud.
- 1
Hold ⌥⌘ and talk
- 2
Lazur looks at your screen and answers out loud.
- 3
You stay in Chrome. Nothing to copy into a chat window.
More things to say in Chrome
- “Hold ⌥ ⌘ and ask what this term means in this paragraph.”
- “Ask where the sample size is reported on this page.”
- “Ask how to turn on the markup toolbar in Preview.”
- “Hold fn and dictate your five-line summary at the cursor.”
- “Ask Lazur to research two other papers on this method and report back.”
- “Ask Lazur to set a 30 minute timer before you start the paper.”
Free for 3 days, then $18/month. Download for Mac
You say“What does this term mean in this paragraph?”
Lazur · explains what's on screenLazur answers out loud from the text on screen. Check the definition against the paper's own wording before you cite it.
What developers say to Lazur for this
Each one is a single hold of ⌥ ⌘.
“Hold ⌥ ⌘ and ask what this term means in this paragraph.”
Lazur looks at the screen while you hold the keys and answers out loud. Check the answer against the paper's own definition.
Explains what's on screen
“Ask where the sample size is reported on this page.”
Lazur draws a circle and a label around the spot on your screen, so you can find it without scanning the page.
Points at it
“Ask how to turn on the markup toolbar in Preview.”
Lazur guides you one click at a time and waits for each click. You still do the clicking.
Walks you through it
“Hold fn and dictate your five-line summary at the cursor.”
Dictation types clean text at your cursor in any app. Dictation is unlimited on Pro and Power.
Types what you say
“Ask Lazur to research two other papers on this method and report back.”
Research runs in Lazur's own Chrome tabs and comes back with a summary and a report. Verify each source yourself.
Researches in the background
“Ask Lazur to set a 30 minute timer before you start the paper.”
Timers are one of the everyday voice actions. A timer keeps the time box visible while you read.
Handles the small stuff
A plan you can start this week
- Day 1
Pick the question and the time box
Choose one paper and write one sentence about what you need from it. Set a 30 minute timer for the first pass. Keep the question in a single note, visible while you read.
- Day 2
Run the 10-minute scan
Read the title, abstract, headings, figures and conclusion. Decide whether the paper answers your question. If it does not, file it and move on without guilt.
- Day 3
Do the focused read
Read the introduction and results closely. Look up each unfamiliar term before the next section. Keep a running list of questions, one line each, in your note.
- Day 4
Check only what matters
Read the methods and limitations only where your question depends on them. Compare the limitations with the strength of the claims. Print any dense page you struggle with, then compare how it felt.
- Day 5
Write, export, and review
Write your five-line summary and save it with the paper. Export Preview annotations to an editable PDF. Note the minutes it took, and decide whether to keep the routine for next week.
Questions people ask
Why can I read a short article easily but not a 12 page paper?
Short articles usually explain one idea and stop. A research paper stacks a question, a method, results and a discussion, and each part depends on the one before. Missing one definition can make the rest harder to follow.
Is reading on paper really better for understanding?
The best evidence I found says paper helps a little on average. A 2018 meta-analysis of 54 studies reports g = -0.21 favoring paper, with a larger gap under time pressure. The effect is modest, and I could not open the original studies.
How long should it take to read a research paper?
In a 2012 survey of US scholars, the average was just over 30 minutes per article. That is an average, not a target. Set a timer for a first pass, then decide whether the paper deserves a full read.
Can Lazur read a PDF for me?
No. Lazur looks at your screen only while you hold the shortcut, and it answers out loud. It does not click buttons, edit files or operate other apps for you. Check its answers against the paper before you cite them.
Can I paste unpublished data into an AI tool?
Follow your employer, lab or ethics board rules first. Lazur sends audio and the screenshot to AI providers to answer you, and they are not stored. Content is never used to train AI models. Remove sensitive details if you are not sure.
Which Mac app should I use to annotate papers?
Preview comes with your Mac and supports highlights and notes. Zotero has its own reader, but its annotations stay in its database unless you export a PDF. Skim lists 1.7.19 as its newest release in the SourceForge folder I checked.
How much does Lazur cost after the trial?
Pro is $18 a month, or $15 a month billed annually, with 150 AI actions. Power is $120 a month, or $96 a month billed annually, with 1,000 AI actions. The 3-day Pro trial needs no credit card. Dictation is unlimited on both plans.
Sources
- Researchers Read Fewer Papers · The Scientist · checked 2026-11-07
- Scientists Reading Fewer Papers for First Time in 35 Years · Scientific American · checked 2026-11-07
- Study shows 66% of researchers overwhelmed by volume of published research · Scientific Computing · checked 2026-11-07
- Don't throw away your printed books (TUM summary of Delgado 2018 and Clinton 2019) · TUM Center for Educational Technologies · checked 2026-11-07
- Annotate a PDF in Preview on Mac · Apple Support · checked 2026-11-07
- Skim release files · SourceForge · checked 2026-11-07
- Zotero PDF reader · Zotero · checked 2026-11-07
Fix reading long research papers with Lazur, free for 3 days
Hold a key and ask. Lazur sees your screen, points at the button and talks you through it, in any Mac app. No credit card.