How Do I Actually Finish CS50? A Realistic 2026 Plan

You finish CS50 by treating the ten problem sets and the final project as the course, and the lectures as the help you need to do them. Our recommendation is about 8 to 10 hours a week for 16 weeks, which fits around a full-time job and ends well before CS50's final deadline of 30 June 2027. Set your own weekly deadline, do the easier version of every problem, and track every score in CS50's Gradebook.

Quick Answer: how do you actually finish CS50?

Commit to about 8 to 10 hours a week for 16 weeks and give every week a problem set deadline you set yourself. Watch one lecture, then spend most of your time on that week's problems. Submit all ten problem sets and the final project with 70% or more on each. That is the whole requirement.

Why most people never finish CS50

Most people stop CS50 because the course rewards work, not watching, and nothing outside you forces the work to happen. The certificate needs every problem set and the final project at 70% or more. With no weekly deadlines and no office hours, the plan has to come from you.

Start with the rule that catches people by surprise. CS50's certificate page says the free CS50 Certificate requires you to submit and score at least 70% on each problem set and on the final project. The CS50x FAQ is blunt. Asked "If I did 70% of the problems, do I get a certificate?", the answer is "No. You must do all the required assignments and receive at least a score of 70% on each." For the certificate, nine out of ten problem sets counts the same as zero.

The second trap is watching. The FAQ also says that watching all the videos does not earn a certificate. By LearnPath's own count from the official playlist, October 2026, Lectures 0 to 10 add up to about 24 hours of video. The problem sets are the real work, and they take much longer than the lectures. It is easy to binge lectures, feel productive, and then stall on Problem Set 1.

The third trap is time. CS50x has no per-assignment deadlines. The only deadline is the end of the course, which the FAQ gives as 11:59 PM UTC on 30 June 2027 for the current term, which began 1 January 2026. The FAQ says it is "best to assume the final deadline is 30 June 2027". A deadline that far away creates no pressure this week, so "this week" quietly becomes "next month".

The fourth trap is the "more comfortable" problems. Early problem sets offer a less comfortable and a more comfortable version. You only need one, and the harder one earns no extra points. The FAQ says it is better to skip the harder version than get so frustrated you drop out, and notes that in the Fall 2019 Harvard class only 20-30% of students submitted the more comfortable problems.

The last trap is being alone. There are no regular office hours. CS50 points you to its communities, starting with CS50.ai and Ed. If you are the kind of learner who drifts during long videos, our guide on how to stay focused in long video lectures covers that part.

What finishing CS50 actually requires

Finishing CS50x means ten problem sets, Problem Set 0 through 9, and one final project, each scored at 70% or more, all before 30 June 2027. There is no test and no final exam. Your scores live in CS50's Gradebook, not on edX, and you can resubmit, with only your latest submission counting.

The checklist, from the syllabus, the certificate page and the FAQ:

1. Register on edX. It is required for either certificate. The free audit option is fine.
2. Submit Problem Sets 0 to 9. Each one needs at least 70%. In weeks with more than one problem, every required problem counts.
3. Know how a score is built. Each problem is 75% correctness, checked by check50, and 25% style, checked by style50. The FAQ's example: check50 at 7/8 and style at 0.95 gives 89%.
4. Do the final project. Any language, alone or with one or two classmates. A solo project should take more time and effort than any single problem set.
5. Submit the project in three steps. A video of no more than 3 minutes on YouTube (unlisted is fine, private is not) plus a form, a README.md, and a submission with submit50.
6. Finish before the deadline. End of day UTC, 30 June 2027.

One more rule: if the deadline is extended, work scored at 70% or more carries forward, but only whole weeks. In weeks with several problems, you must complete all of them for the week to count.

Your realistic options, compared

There are five realistic ways to take on CS50x, from the free self-paced course to Harvard Extension School for credit. They differ in cost, in structure and in how much outside pressure they add. Pick the one that will actually get your problem sets submitted.

Prices come from Harvard's CS50 course listing, CS50 at Harvard Extension School and the Extension School's undergraduate coding certificate page, whose undergraduate coding certificate track starts with CSCI E-50. CS50P is CS50's Introduction to Programming with Python, and CS50 itself says you can take it before, during or after CS50x, "But for an introduction to computer science itself, you should still take CS50x!"

The honest summary is that the free course is enough. CS50x via OpenCourseWare is the full course with the full problem sets, and the free CS50 Certificate comes from CS50's own Gradebook. Paying for edX verification or Extension credit buys a different credential, not easier problem sets. If you need a deadline that someone else enforces, Extension is the only row here that gives you that.

LearnPath is one row in this table, not the answer to it. It builds a path of YouTube lessons in order and puts a quiz after each lesson. On the Free plan you get step 1 of each path, for up to 2 paths. Later steps, unlimited paths and the LearnPath completion certificate are on Pro at $12.99/month or $8.99/month billed annually. That Pro certificate is not a CS50 or Harvard certificate. The only way to the CS50 Certificate is CS50's own Gradebook, through the problem sets and the final project.

A 16-week plan to finish CS50x

This is our recommended plan: about 8 to 10 hours a week for 16 weeks, built for someone with a job. One lecture, then that week's problem set, every block. The early C weeks, Memory and Data Structures get two weeks each because they are the densest C weeks. The last three weeks are for the final project.

Each block runs the same way: the lecture, then the section and shorts if you need them, then the problem set. Every lecture is free on the CS50 channel and in the official CS50x Lectures playlist. Set a submit date for each block and keep it.

Weeks 1-2: Lecture 0 and Lecture 1 (Scratch and C)

Watch CS50x - Lecture 0 - Scratch, about 2 hours, and submit Problem Set 0 in the first few days. Then watch CS50x - Lecture 1 - C, about 2.5 hours, and spend the rest of week 2 on Problem Set 1. This is enough because Scratch builds the habit of submitting, and Problem Set 1 is your first real fight with C syntax. Pick the less comfortable problems.

Weeks 3-4: Lecture 2 (Arrays)

Watch CS50x - Lecture 2 - Arrays, about 2.4 hours, and give Problem Set 2 two full weeks. Two weeks is enough because the goal is a passing submission and a little more comfort with C, not mastery.

Week 5: Lecture 3 (Algorithms)

Watch CS50x - Lecture 3 - Algorithms, about 2 hours, and submit Problem Set 3. One week is enough here because you already know the C basics, and this week is about applying them. If a problem drags, submit a working version first and fix style later.

Weeks 6-7: Lecture 4 (Memory)

Watch CS50x - Lecture 4 - Memory, about 2.3 hours, and give Problem Set 4 two weeks. Memory is the densest week of C in the course, so the extra week is the point.

Weeks 8-9: Lecture 5 (Data Structures)

Watch CS50x - Lecture 5 - Data Structures, about 2 hours, and give Problem Set 5 two weeks. This is the last hard C week. Two weeks is enough because it builds directly on Memory.

Week 10: Lecture 6 (Python)

Watch CS50x - Lecture 6 - Python, about 2.5 hours, and submit Problem Set 6. One week is enough because the C weeks already taught you to think like a programmer.

Week 11: Lecture 7 (SQL)

Watch CS50x - Lecture 7 - SQL, about 2.25 hours, and submit Problem Set 7. One week is enough because the goal is a passing submission.

Week 12: Lecture 8 (HTML, CSS, JavaScript)

Watch CS50x - Lecture 8 - HTML, CSS, JavaScript, about 2.4 hours, and submit Problem Set 8. One week is enough because the goal is a passing score, not a beautiful page.

Week 13: Lecture 9 (Flask)

Watch CS50x - Lecture 9 - Flask, about 2.4 hours, and submit Problem Set 9, your last one. One week can feel tight, because Flask builds on the Python, SQL and HTML weeks before it. If it runs over, borrow a few days from the project weeks.

Weeks 14-16: Lecture 10 (The End) and the final project

Watch CS50x - Lecture 10 - The End, about 52 minutes, then build your final project. Read the spec first: the FAQ says the top reasons for failing are not following it and a README that is too thin. Pick a small idea. In the last week, record a video of no more than 3 minutes and upload it to YouTube as unlisted, fill in the form, write a README.md (CS50 says one in the neighborhood of 750 words is likely to be sufficient), and submit with submit50.

If you start in mid-October 2026, a 16-week plan ends months before the 30 June 2027 deadline. That buffer is on purpose, for the sick week or the stubborn problem set.

What to skip

Skipping the right things is what keeps a 16-week plan at 16 weeks. Skip the harder problem versions, full lecture rewatches, general-purpose AI assistants on problem sets, the edX progress bar and the urge to switch courses. None of them moves a score in your Gradebook, and some can disqualify you.

Skip the "more comfortable" versions. You only need one version, and the harder one earns no extra points. CS50's own FAQ tells you to skip it rather than drop out.

Skip rewatching lectures end to end. A full rewatch feels like study but rarely fixes your bug. Find the few minutes that cover your problem and go back to the code.

Skip general-purpose AI assistants on problem sets. CS50's academic honesty policy says using AI-based software other than CS50's own that suggests or completes answers or lines of code is not reasonable, and neither is searching for outright solutions. CS50's own AI-based software, including the CS50 Duck in cs50.ai and cs50.dev, is allowed. The final project page adds that staff audit submissions and that violations make you ineligible for a certificate, including on edX. It also says that for the final project only, other AI-based software is reasonable if the essence of the work is your own and you cite it in code comments.

Skip the edX 0% grade. edX shows 0%. Your real progress is in CS50's Gradebook.

Skip hopping to other courses. When C gets hard, another beginner course looks easier, and starting over leaves CS50 unfinished. That loop has a name, and we wrote about breaking it in how to get out of tutorial hell. The one sensible detour is CS50P, and only if you decide before you start that C is too steep a first step.

How to know you are on track

You are on track if every finished block shows a score of 70% or more in CS50's Gradebook by the date you set for it. The rule is simple: one problem set submitted per block, no week left half done, and the final project started by week 14.

Use these checks at the end of each block:

1. The Gradebook shows the score. Every required problem for the week is submitted and at 70% or more.
2. You are no more than one block behind. The buffer covers one. Two blocks behind means cut extras, like the shorts, until you catch up.
3. The hard weeks are on schedule. If Problem Set 5 is in by the end of week 9, the rest of the course is lighter.
4. You can explain your own code. If you cannot explain a line you submitted, the next week will be harder.

Proof at the end

When your last required score lands, CS50 gives you a free CS50 Certificate from your Gradebook. You can also pay edX $219 for a verified certificate. Either way, the proof that matters most is a working final project and ten problem sets you solved yourself.

The FAQ says the free CS50 Certificate link appears in your Gradebook within about four hours of your last required score. Download it before the deadline. If you also want the edX verified certificate, you can pay for verification up to 10 days before the final deadline, CS50 recommends verifying before you finish, and it can take up to 30 days to be issued. Whether a certificate is worth paying for at all is a separate question, and we cover it in are certificates worth it for self-taught developers.

If you also use LearnPath for another topic after CS50, its certificate is on Pro and is not a CS50 or Harvard certificate.

Frequently Asked Questions

How do I actually finish CS50 without quitting halfway?

Treat the problem sets as the course, not the lectures. Set your own deadline, give about 8 to 10 hours a week for roughly 16 weeks, do only the less comfortable version of each problem, and submit every week. Track progress in CS50's Gradebook, and leave two to three weeks at the end for the final project.

How long does it take to finish CS50x?

Harvard's course listing says 10 to 20 hours per week, self-paced. Our recommendation for someone with a job is about 8 to 10 hours a week for about 16 weeks, with extra time on the C, Memory and Data Structures weeks. The lectures alone are about 24 hours of video, but the problem sets take far longer.

Is the CS50 certificate free?

Yes. CS50 gives a free CS50 Certificate to anyone who submits all ten problem sets and the final project with at least 70% on each. You must register on edX, and the free audit option is enough. edX also sells an optional verified certificate for $219, which you can pay for up to 10 days before the deadline.

Can I use AI tools on CS50 problem sets?

Only CS50's own. The academic honesty policy allows CS50's AI-based software, including the CS50 Duck in cs50.ai and cs50.dev. Using other AI-based software that suggests or completes answers or lines of code is not reasonable. The final project is the one exception, if the essence of the work is yours and you cite it in comments.

Do I have to do the more comfortable problems in CS50?

No. In weeks that offer a less comfortable and a more comfortable version, you only need one, and the harder one earns no extra points. CS50's own FAQ says it is better to skip the harder version than get so frustrated that you drop out. Pick the less comfortable version and keep moving.

Should I take CS50P before CS50x?

Only if C feels like too big a first step. CS50P is CS50's Introduction to Programming with Python, also free via OpenCourseWare, with ten weeks of material entirely in Python. CS50 says you can take it before, during or after CS50x, but for an introduction to computer science itself, you should still take CS50x.

The bottom line

CS50 is hard to finish because nothing makes you submit this week. Give yourself 16 weeks, about 8 to 10 hours each, one problem set per block, and the easier version of every problem.

Give CS50 a finish line: put your Problem Set 0 submit date in your calendar tonight, and build a path for the topic you take on after CS50 before your next sprint starts, so the momentum has somewhere to go.