YouTube Playlist Analyser

What this tool does

YouTube Playlist Analyser is a free YouTube playlist length calculator and study planner. Paste any public playlist link and it adds up the runtime of every video, so you know the total duration before you commit to a course.

Most calculators stop there. This one goes a step further: it turns that total into a realistic day-by-day schedule. Tell it how many minutes you can study each day and it works out how many days the playlist will actually take — at normal speed and at faster playback speeds.

YouTube itself shows a video count and each video's duration, but never the sum. On a 12-video playlist you can add it up in your head. On a 240-video lecture series you can't — and that's exactly where the number matters, because that's where you're deciding whether to commit weeks of your life. The absence is probably deliberate: a platform optimising for watch time has little reason to open a session with "this will take you 94 hours."

It's built for anyone working through a long playlist: a programming course, a lecture series, an exam-prep channel, or a documentary backlog. Instead of a vague "this looks long," you get a concrete finish date.

How to use it

1. Paste your playlist link

   Copy the playlist URL from YouTube and paste it in the box above. A raw playlist ID (the PL… part) works too. Links that include &list= from a video page are fine — we pull the playlist out automatically.

2. Set your daily study time

   On the next screen, enter how many minutes a day you can realistically watch, and choose which playback speeds to compare (for example 1, 1.5, 2).

3. Get your schedule

   You'll see the total playlist length plus a full day-by-day breakdown for each speed — which videos to watch on which day, and how many days to finish.

Source length vs. watch time

Almost every confused question about playlist length comes from conflating two quantities that are only equal at 1x speed:

• Source length — the sum of the videos as published. A fixed property of the playlist, and what a calculator reports.
• Watch time — how many hours out of your life it costs. Source length divided by your playback speed.

A 30-hour playlist watched at 1.5x has a source length of 30 hours and a watch time of 20 hours. Both are "the length of the playlist." Only the second is the number to plan your week around.

watch time = source length ÷ speed

Where the durations come from

There are two ways to get a playlist's durations, and they are not equally reliable.

Scraping the page

The cheap method: load the playlist page and read the duration badges off the thumbnails. No API key, no quota. It also breaks whenever YouTube changes its markup, silently truncates at the ~100 videos the page loads before you scroll, and reads durations already rounded for display.

The YouTube Data API

The reliable method, and the one this site uses. Two endpoints are involved:

• playlistItems returns the playlist's contents in order, 50 at a time. For 240 videos that's 5 sequential requests. This gives video IDs — not durations.
• videos takes up to 50 IDs per call and returns contentDetails.duration for each, which is authoritative to the second.

Durations arrive as ISO 8601 strings: PT1H23M45S is one hour, 23 minutes, 45 seconds. PT9M is a flat nine minutes — the format omits zero components, which is a common source of parsing bugs in home-rolled calculators. Summing the parsed seconds gives the total.

The practical upshot: an API-based total is accurate to the second at any playlist length but consumes a daily quota, while a scraped total is free and unlimited but quietly wrong on long playlists. If a calculator returns a suspiciously round number on a 300-video playlist, suspect truncation.

What gets counted, and what doesn't

Most disagreements between calculators come down to this table rather than to arithmetic.

This is why a playlist of 200 videos may analyse as 193: seven entries are dead slots that YouTube still displays. It also means your average-video-length figure depends on using the right denominator — divide by watchable videos, not by playlist slots.

Does watching faster actually save time?

Yes — but the savings are non-linear in a way that trips people up. Going from 1x to 1.25x saves 20% of your time, not 25%, because the increase applies to the rate rather than to the duration. Each further step up the dial buys less than the one before.

Compare the rows: 1x to 1.5x saves 33% of the original, while 1.5x to 2x saves only another 17%. Most of the available gain sits in the lower half of the dial — which matters, because comprehension tends to fall off fastest at the top end. You pay the steepest cost for the smallest remaining benefit.

A practical note: speed works best for lecture-style talking-head content. For dense material — heavy maths, live coding you're following along with — many people find 1.25x is the ceiling before they start re-watching sections, which cancels out the gain. That's why this tool shows several speeds at once, so you can weigh comprehension against the calendar rather than guessing.

From hours to a finish date

A total in hours is still abstract. Divide it by what you'll actually watch per day:

days = watch time ÷ daily watch time

Take a 42-hour programming course at 1.5x, 45 minutes a day:

1. Source length: 42 hours = 2,520 minutes.
2. At 1.5x, watch time is 2,520 ÷ 1.5 = 1,680 minutes, or 28 hours.
3. At 45 minutes a day: 1,680 ÷ 45 = 37.3, so 38 days.

One honest caveat about that 38: it assumes 38 consecutive days without a miss, and nobody does that. Planning at five or six study days a week turns it into roughly seven calendar weeks — a figure that survives contact with reality far better.

Building a day-by-day plan

The planner starts from a single quantity, your daily capacity — how much source material one day's studying consumes:

daily capacity = daily minutes × playback speed

This reads backwards at first glance. Why would watching faster increase capacity? Because capacity is measured in source material, not in your time. Your 60 minutes is fixed; at 1.5x those 60 minutes get you through 90 minutes of lectures. Faster speed means more of the playlist fits into the same sitting.

The planner then walks the playlist in order and fills day one until capacity is used up, starts day two, and continues to the end. Playlist order is preserved throughout — courses are sequenced for a reason, and a planner that reordered videos to pack days more neatly would be optimising the wrong thing.

Whole videos or split videos

One real decision shapes the output. Both options are defensible; they fail in different directions.

Whole videos only. A video is never divided across a day boundary. If 12 minutes of capacity remain and the next video runs 40 minutes, the day ends early and that video opens tomorrow. Good for playlists of self-contained episodes, and for anyone who finds stopping mid-explanation costly — every session ends at a natural boundary. The cost is uneven days: with long videos and a short daily target, some days run well under your intended time.

Allow splitting. A video can carry over, so the planner tracks how many seconds of it you've already consumed and resumes mid-video the next day. Day two might begin 18 minutes into lecture 7. Good for long-form lectures and anything where you want each day to hit a consistent length. The cost is that you need to note your stop timestamp, and you'll sometimes break mid-derivation.

A rule of thumb: if your average video is comfortably shorter than your daily target, use whole videos — the unevenness will be minor and you get clean boundaries for free. If individual videos routinely exceed your daily target, splitting isn't optional, because without it one video simply becomes one day regardless of its length.

A worked example

A 60-video course, 28 hours of source material, average video 28 minutes. You have about 45 minutes a day on weekdays and you're comfortable at 1.5x.

1. Daily capacity: 45 × 1.5 = 67.5 source minutes per day.
2. Total: 28 hours = 1,680 source minutes.
3. Study days needed: 1,680 ÷ 67.5 = 24.9, so 25 study days.
4. At five study days a week: 25 ÷ 5 = five calendar weeks.

Note what the split setting does to this. With 67.5 minutes of capacity and 28-minute videos, whole-video packing fits two videos per day (56 minutes) and wastes the remaining 11 — stretching those 25 days to around 30. Allowing splits recovers that, which over a 28-hour course is most of a week. The longer the videos relative to your daily target, the more the toggle matters.

Choosing a daily target that survives

The most common planning mistake isn't arithmetic, it's ambition. People set the daily target at their best possible day, then miss it twice and abandon the plan. Some things that help:

• Plan from your median day, not your best one. If you managed 90 minutes once and 30 minutes most days, your number is 30–40, not 90. A plan you follow at 35 minutes finishes sooner than a plan you abandon at 90.
• Budget five or six study days a week. A 40-day plan at seven days a week is really closer to eight calendar weeks. Building the slippage in up front beats discovering it in week three.
• Account for the pausing tax on technical material. If you stop to take notes or type along with code, an hour of wall-clock time might cover 35 minutes of video. Either set the daily minutes to the video time you'll actually get through, or plan at 1x and treat any speed-up as slack.
• Re-plan rather than catch up. After falling behind, recalculating from where you actually are gives you a current finish date. Trying to make up a deficit on top of a target you were already missing tends to end the project.

Where hand-calculated totals go wrong

Rounding before summing

The big one. Round each video to the nearest minute and the errors accumulate: across 200 videos, an average rounding error of 15 seconds is 50 minutes of drift — enough to misplace a whole study day. Sum in seconds, convert once at the end.

Treating the playlist page as complete

YouTube loads playlists in pages. If you're reading durations off the screen, you're reading the first batch only, and your total will be confidently short.

Counting dead slots

Deleted and private videos still occupy visible positions and contribute nothing to the duration, so the slot count overstates what you'll actually watch.

Estimating from an average on mixed-format playlists

Sampling ten videos and multiplying by the count lands within 10–15% on a consistent course playlist. On a conference channel with 8-minute lightning talks beside 3-hour keynotes there is no meaningful "average video," and sampling will mislead you badly in whichever direction your sample was biased.

What a schedule can't do for you

Worth saying plainly: a day-by-day plan solves the planning problem, not the learning problem. Finishing a playlist on schedule and understanding it are different achievements, and the schedule only measures the first.

Watching is the passive part of learning, and it's the part a planner can help with. Retention comes from the active part — writing something down without looking, rebuilding a project from memory, explaining a concept aloud, coming back to week one's material in week three. None of that appears in a duration calculation, and for dense material it may well take as long again as the watching does. If your plan says five weeks, the honest figure for actually knowing the material is longer.

Features

Who it's for

• Students planning revision around an exam date.
• Self-taught developers working through a long programming course.
• Anyone taking a free course on YouTube who wants a finish date instead of an open-ended backlog.
• Bootcamp and MOOC learners checking whether a playlist fits the time they actually have.
• Curious viewers who just want to know how long a playlist is before starting it.

Frequently asked questions