How long does Unity take to learn? The course's own numbers

the short answer

How long does it take to learn Unity and make a game?

All 40 lessons here add up to 447 minutes — 7.45 hours — counted straight from the minutes field in curriculum.ts. Do the five end-of-tab exercises as their own briefs ask and the honest total is 18–23 hours.

Almost every answer to “how long does Unity take to learn” on the internet is an opinion. This one is arithmetic: the minutes field on all 40 lessons of this course, summed, plus the hours the five exercises ask for themselves. Below is that table, the division for a 30-minutes-a-day plan, where other people's numbers come from, and the line past which these numbers stop describing you.

The short answer

First scene on screen: minute 35 of the course. Lesson 06 is one Plane, one material and a camera, and it is 8 minutes long. Add the time to install Unity Hub and the editor — the curriculum does not count that.
First thing you actually control: minute 64. Lesson 09 swaps three characters with 1/2/3 on the floor you just built — the milestone the home page leads with.
The whole course, lessons only: 447 minutes = 7.45 hours. That is every minutes field in curriculum.ts added up. The home page prints “about 7 hours” because it rounds.
Lessons plus doing the five exercises as their own briefs ask: 18–23 hours. The 35 teaching lessons are 335 minutes; the five exercise pages state 60–90 minutes, then 3–4, 2–3, 3–4 and 3–5 hours. Add them and the range is 17.6 to 23.1.
Your own game, alone, from an empty folder to a published build: no number on this page reaches there, and the reason is scope, not Unity. The closest the curriculum can say is this — a second game that reuses exactly what two stages teach, moving and jumping between blocks, three skills on cooldown, enemies that chase and hit back, then an APK on a real phone, costs about the two exercise pages holding those parts: tab 02's 3–4 hours plus tab 05's 3–5, so 6–9 hours. With art you did not make. Every mechanic this course does not teach sits outside that figure.

One thing this list deliberately does not contain: how long until a salary, how long until a job. That is not the same question as how long Unity takes, and anyone answering it in a blog post does not have your data.

This course's own numbers

Every figure below is read out of curriculum.ts: how many lessons a tab has, and the sum of their minutes. The exercise row of each tab is inside that sum, because it carries a minutes value like every other lesson — and it is also the least useful number in the file, so the last column quotes what the exercise page itself asks for.

Metric	Target	Why
Tab 01 · Basics & Arena — lessons · minutes	11 · 100	1.7 hours. The exercise row says 20 minutes; the brief at the top of it asks for 60–90.
Tab 02 · Character & Combat — lessons · minutes	9 · 114	1.9 hours. The exercise row says 24 minutes; its brief says 3–4 hours.
Tab 03 · Camera & Input — lessons · minutes	6 · 67	1.1 hours. The shortest tab. The exercise row says 20 minutes; its brief says 2–3 hours.
Tab 04 · World & Game Loop — lessons · minutes	7 · 83	1.4 hours. The exercise row says 22 minutes; its brief says 3–4 hours.
Tab 05 · Export to Mobile — lessons · minutes	7 · 83	1.4 hours. The exercise row says 26 minutes; its brief says 3–5 hours, and that one ends with an APK on a real phone.
All five tabs — lessons · minutes	40 · 447	7.45 hours of lessons, which the home card rounds to about 7 — and separately tells you to add the 5 exercises.

Here is the exact arithmetic the home page runs, so you can check it against the file instead of against this article.

The timing card, counted from TABS rather than typed in

const minutes = TABS.flatMap((tab) => tab.lessons.map((l) => l.minutes));
minutes.length;                                     // 40 lessons
const total = minutes.reduce((a, b) => a + b, 0);   // 447 minutes
Math.round(total / 60);                             // 7    the "about 7 hours" card (7.45 rounded)
Math.round(total / 30 / 7);                         // 2    weeks at 30 min a day, every day
Math.min(...minutes) + "-" + Math.max(...minutes);  // 4-26 minutes per lesson

What 30 minutes a day adds up to

Lessons only: 447 ÷ 30 = 14.9 sessions. Fifteen half hours and you have been through all 40 lessons. That is the “about 2 weeks” the home card prints, Math.round(447 ÷ 30 ÷ 7) — and it assumes you study every day.
Take the weekends off and the same 14.9 sessions become 3 weeks: 14.9 ÷ 5.
Now add the exercises, which the site separately tells you to add: 17.6–23.1 hours = 1,055–1,385 minutes = 35–46 sessions. Every day: 5–6.5 weeks. Five sessions a week: 7–9 weeks. That is the honest answer to the question — one to two months of daily half hours.
Is 30 minutes even enough for one lesson? Yes, and only just: the average is 447 ÷ 40 = 11.2 minutes, and the range on the home card is 4–26. The 20–26 minute exercises fill a session by themselves.
Different split, same minutes: 45 minutes on four evenings is 180 minutes a week — the lessons in 2.5 weeks, lessons plus exercises in 6–8 weeks. Divide the total by the week you actually have, not the week you meant to have.

Why other people's numbers are different

2D or 3D. This course is 3D: a CharacterController sliding along colliders, a camera with three axes to tame, lightmaps, LOD, draw-call budgets. The two-week claim you read is usually about 2D — sprites, a Tilemap, movement on one plane. This course's own home page lists 2D and sprites under “what it does not cover”, so its 447 minutes are not comparable to a 2D figure.
Art handed to you, or art made by you. Every number above is code and scene work, and it only comes down to 447 minutes because capsules are allowed — “no 3D modelling, a capsule is enough” is a real line on this site. Model, rig and animate one character that walks, attacks and reacts to being hit, and none of the tables above describe your week.
Someone checking your work, or nobody. Each of the five exercises ends in a checklist that defines what “done” means, and nothing on this site ticks it for you. A mistake made in tab 02 tends to surface in tab 04, and by then the cost is not the ten minutes it took to make but the afternoon it takes to find.
And the cheapest lever, which costs no study hours at all: shrinking the game. No route takes 18–23 hours down to five by making you learn faster. One arena, one screen, three enemies, no side menus, no cloud save — that is a finishable game, and these five tabs were cut to exactly that shape.

Every number on this page is a time, not a wage. A page that tells you how many months until you are hired, then offers a bootcamp on the next line, wrote the first sentence for the sake of the second.

Signs you are going slower than you need to

The tutorial loop: you finish one course and open the next without ever opening your own project. The test is one folder — how many scenes in your Projects folder run without a video beside them? Zero after six months means the loop, and no new material breaks it. Only shipping something ugly does.
Changing engines every time the current one stops being fun. Each switch teaches you how that editor opens a project, not a new game mechanic. The thing that made you stall in Godot is just as hard in Unity.
Never finishing. Three projects at ninety percent cannot be played, shown to anyone, or learned from; one build on a real phone can. This course sets aside 3–5 hours of its own for that last step — a deliberately small number, so nobody keeps an excuse for skipping it.
Reading code instead of typing it. The code block in every lesson exists to be retyped, run, and broken once on purpose. Skipping ahead because you followed the idea costs you the only part that transfers to the next project.

The shortest road that is not a shortcut

1
One project, one scene. This course grows a single Arena.unity across all five tabs: the floor you make in tab 01 is the floor the finished build runs on in tab 05. Nothing gets thrown away, and no lesson is a throwaway example.
2
All five tabs in order, no skipping: 100 → 114 → 67 → 83 → 83 minutes. Each one ends in an exercise, and the exercise is where reading turns into skill — which also makes it the thing that looks cheapest to skip and bills you the most.
3
Ship it to a real device. Tab 05 is 57 minutes of lessons plus an exercise row of 26 — and a brief that asks for 3–5 hours, ending with an APK running on your own phone. When you get there, that step has its own guide, linked at the end of this page.
4
Write down the hours you actually used. The course predicts 18–23. Yours is the only figure that will describe your next project, and it is the one thing this curriculum genuinely does not measure.

Checklist, in this order

✓You have one project, not two. A second one is sign number one from the section above.
✓All 35 teaching lessons read, none scrubbed past: 335 minutes on paper.
✓Stage 01 done: floor, blocks spawned by code, three characters on 1/2/3 — the 60–90 minutes its own brief asks for.
✓Stages 02–04 done: you jump between the blocks, lose a fight to three enemies, drive the whole thing with one thumb, and the dressed arena holds 60 FPS.
✓Stage 05 done: an APK that installs on your phone and runs with the editor closed.
✓Your real hours written down and set against 18–23. The gap between them is the number for your next game.

Lesson 01 is four minutes long and assumes you have never written a line of code; by minute 35 there is a 3D scene on the screen. When you reach the last tab, getting that build onto a real phone has its own guide: From project to APK on a real phone.

the lesson that builds this

C# in 60 seconds: variables

This post is a standalone recipe. In the course, the same thing is built as part of the one project that runs through all five tabs — Basics, lesson 01.