Calculateur de temps de lecture
Calculez le temps nécessaire pour lire un texte à une vitesse donnée.
À propos du calculateur de temps de lecture
Medium, Substack et la plupart des plateformes de contenu affichent des temps de lecture estimés. L'adulte moyen lit environ 200 à 250 mots par minute pour des textes non fictionnels. Ajustez le curseur MPM selon votre audience — la documentation technique est généralement lue plus lentement que la prose narrative.
FAQ
- Quelle est la précision de l'estimation ?
- C'est une estimation basée sur le nombre de mots et le MPM choisi. La complexité, la mise en forme et les images affectent le temps de lecture réel.
- Quel MPM dois-je utiliser ?
- 200 MPM est une bonne valeur par défaut pour le grand public. Les lecteurs techniques peuvent être plus proches de 150 à 175. Les lecteurs rapides peuvent atteindre 400+ MPM.
- Qu'est-ce qu'une « page imprimée » ?
- Calculée à 275 mots par page, ce qui est une estimation courante pour une mise en forme standard de livre/article.
À PROPOS DE CET OUTIL
Paste any block of text and get an estimated reading time based on an average or custom reading speed in words per minute. Bloggers and content editors use it to set reader expectations before publishing long-form articles. The estimate is calculated by dividing the total word count by a reading speed you can adjust, since the commonly cited average adult silent-reading speed sits somewhere around 200-250 words per minute but varies a lot by content difficulty, language, and individual reader. Adjusting the words-per-minute input lets you model faster skimmers or slower technical readers instead of relying on one fixed number.
COMMENT UTILISER
- Paste the full article or text you want to estimate reading time for
- Check the default words-per-minute speed the tool uses
- Adjust the words-per-minute value if you want to model a faster or slower reader
- Review the estimated reading time shown for the pasted text
- Recalculate after edits as you trim or expand the draft
CAS D'USAGE COURANTS
- A blogger adding a '7 min read' label to a post before publishing
- A newsletter writer checking whether an issue is short enough to read during a coffee break
- A YouTube scriptwriter estimating how long a voiceover script will take to read aloud versus its target video length
- An academic checking how long a paper's abstract will take reviewers to read through
- An e-learning content creator estimating time-on-page for a lesson to plan a course schedule
CONSEILS ET ERREURS COURANTES
- The default words-per-minute figure is an average — technical, dense, or unfamiliar-vocabulary text is read more slowly than casual prose, so lower the WPM input for jargon-heavy content
- This tool counts only words in the text box, so it won't account for time spent viewing embedded images, videos, or code blocks within an article
- Reading time estimates are meant for setting rough reader expectations, not for precisely timing a script — spoken reading speed for voiceover work is typically slower than silent reading speed
- If your audience skews toward skimming rather than deep reading (common for blog posts vs. academic papers), consider using a higher WPM value than the default
AUTRES QUESTIONS
- What words-per-minute speed does the calculator use by default?
- It defaults to a commonly cited average adult silent-reading speed, generally in the 200-250 WPM range, but you can override this with a custom value to match a specific audience or purpose.
- Does reading time account for images, videos, or interactive content in an article?
- No, the estimate is based purely on the word count of the text you paste in — visual or embedded media isn't factored into the time unless you manually add extra time for it.
- Is reading time calculated differently for other languages?
- The calculation itself is the same word-count-divided-by-speed formula, but average reading speeds vary by language and script, so a WPM figure tuned for English prose may not be accurate for other languages without adjusting the input.
- Should I use a different WPM for a script meant to be read aloud versus read silently?
- Yes — spoken delivery is generally slower than silent reading, so for voiceover or presentation scripts, lowering the WPM value gives a more realistic estimate of actual runtime.