The 2025 AP Computer Science Principles exam lands on Thursday, May 15, 2025, at 12:00 PM local time.
That's it. That's the date. You can stop scrolling if that's all you needed.
But if you're a student, parent, teacher, or counselor trying to plan the next few months — study schedules, create task deadlines, college application timelines — you'll want the full picture. Because the exam date is only the starting line.
What Is AP Computer Science Principles
AP CSP isn't your traditional coding class. It's broader. Worth adding: the College Board designed it to be an introduction to the ideas* of computing — not just syntax. In practice, you'll cover data, algorithms, the internet, cybersecurity, programming, and the global impact of technology. Think of it as "computer science for everyone," not just future software engineers.
The course has two main assessment pieces:
The Create Performance Task
This is the part you complete during* the course. You build a program — any program that solves a problem or expresses an idea — and then you document it. Written responses, a video of your code running, and the code itself. It's submitted digitally through the AP Digital Portfolio.
Deadline for 2025: April 30, 2025, at 11:59 PM ET.
That's hard. No extensions. If your school has an earlier internal deadline, that's the one that actually matters.
The End-of-Course Exam
Two hours. Multiple choice. 70 questions. No calculator. This is the part happening on May 15.
The exam covers five big ideas:
- Creative Development
- Data
- Algorithms and Programming
- Computer Systems and Networks
- Impact of Computing
Roughly 30% of questions are single-select multiple choice. Consider this: the rest are "multiple-select" — choose two answers. Worth adding: that format trips people up. More on that later.
Why the Date Actually Matters
You might think: It's just a date. I'll study before then.*
But the May 15 date sits in a crowded neighborhood. On the flip side, aP World History is May 14. Also, aP Biology is May 12. In real terms, aP Physics 1 is May 16. Consider this: aP English Language is May 14. If you're taking a typical load of 3–5 APs, you're looking at back-to-back-to-back exams.
And here's what most people miss: the Create Task deadline (April 30) is two weeks before the exam.
That means your final push for the performance task overlaps with your start* of serious exam prep. So you don't get to finish the task, take a breath, then study. You're doing both at once.
Teachers know this. But not every school does that. Good ones structure the spring semester so the Create Task wraps by early April, leaving a clean runway for review. If yours doesn't — you need to build your own runway.
How the Exam Works (and How to Prepare for It)
The Format, Broken Down
Section I: Multiple Choice (70 questions, 120 minutes)
- ~50 single-select questions
- ~20 multiple-select questions (choose 2)
- No penalty for guessing
- Covers all five big ideas, weighted roughly equally
Section II: Create Performance Task (submitted separately)
- Not part of the May 15 exam day
- Scored separately, then combined for your final 1–5 score
What "Multiple-Select" Actually Looks Like
Most students have never seen this format before AP CSP. A question might ask:
Which of the following are benefits of using a procedure (function) in a program? Select two answers.
A) Reduces code duplication
B) Increases execution speed
C) Improves readability
D) Eliminates the need for variables
The answer is A and C. But if you only pick one? Zero points. Still, zero points. Here's the thing — if you pick three? You must* select exactly the number asked.
Practice this format. It's not intuitive. The College Board releases sample questions — use them.
The Reference Sheet Is Your Friend
You get a reference sheet on exam day. )
- List operations (APPEND, REMOVE, LENGTH, etc.It includes:
- Pseudocode commands (DISPLAY, INPUT, IF/ELSE, REPEAT, etc.)
- Robot commands (MOVE_FORWARD, ROTATE_LEFT, etc.
Don't memorize syntax. On top of that, the exam tests logic, not memorization. That said, learn to read* the reference sheet fast. But you waste time if you're hunting for RANDOM(a, b) syntax during the test.
If you found this helpful, you might also enjoy ap computer science exam score calculator or most common errrors ap computer sciecen a exam.
Programming Language: Doesn't Matter
The exam uses pseudocode. Plus, your class might use Python, JavaScript, Scratch, Snap! Worth adding: , or something else. It doesn't matter. The concepts transfer. What does* matter: you understand variables, conditionals, loops, lists, procedures, and boolean logic well enough to trace pseudocode on paper.
Common Mistakes (What Most People Get Wrong)
1. Treating the Create Task Like Homework
It's not. It's 30% of your AP score. The rubric is specific. The written responses have strict word counts and specific prompts. Students who wing it — or copy code they don't fully understand — get burned.
Read the Create Task Directions* and Scoring Guidelines* on AP Central. Which means then read them again. Build your program around* the prompts, not the other way around.
2. Ignoring the "Impact of Computing" Big Idea
It feels like the "soft" unit. It's not. It's 20% of the exam. Questions about bias in algorithms, digital divide, intellectual property, crowdfunding, citizen science — they show up. And they're often the easiest points on the test if you've actually read the material.
3. Cramming Pseudocode Syntax
You don't need to memorize REPEAT n TIMES { } vs REPEAT UNTIL (condition) { }. You need to recognize what each does when you see it. Spend your time tracing code, not memorizing brackets.
4. Forgetting the Digital Portfolio Deadline
April 30, 11:59 PM ET. Not "end of day." Not "when my teacher grades it." The College Board's server timestamp is the only one that counts. Submit by April 28 to sleep easy.
5. Assuming a 5 Is "Easy" Because the Pass Rate Is High
The pass rate (3+) hovers around 70–75%. But the 5 rate? Usually 12–15%. A 3 is "qualified." A 5 is "extremely well qualified." If you're aiming for credit at a selective college, you need a 4 or 5. That takes more than showing up.
Practical Tips (What Actually Works)
Build a Reverse Calendar
Start from May 15. Work backward.
- May 1–14: Full practice exams, timed. Review every wrong answer.
- April 15–30: Create Task done* by April 15. Submit early. Then pure exam prep.
- **March 1–
April 30**: Weekly concept drills — trace 10 pseudocode snippets per session, focusing on list mutations and loop boundaries.
- February 1–28: Cover Big Idea 3 (Algorithms) and Big Idea 4 (Programming) through hands-on exercises, not lectures.
Trace, Don't Guess
When you see a block like:
listScores ← [80, 90, 75]
APPEND(listScores, 95)
REMOVE(listScores, 1)
DISPLAY(LENGTH(listScores))
Don't eyeball it. Step through: starts with 3 items, appends to make 4, removes index 1 (the 90), length is now 3. Even so, output: 3. Do this daily for 10 minutes and the logic becomes automatic.
Use the Reference Sheet Like a Cheat Sheet (Because It Is)
The AP provides a pseudocode reference. Keep it open while you study. Practice finding commands fast:
IF userInput = "left" THEN
ROTATE_LEFT()
ELSE
MOVE_FORWARD()
END IF
If a question shows a robot navigating a grid, you should locate ROTATE_LEFT and MOVE_FORWARD on the sheet within 5 seconds — not 30.
Simulate the Create Task Under Pressure
Set a 60-minute timer. Build a small program that uses a list and a loop. Example prompt: "Track daily steps and alert if below goal."
steps ← []
REPEAT 7 TIMES
INPUT daySteps
APPEND(steps, daySteps)
END REPEAT
REPEAT FOR EACH s IN steps
IF s < 5000 THEN
DISPLAY("Low day")
END IF
END REPEAT
Then write your written responses without exceeding the word limits. Most students lose points here, not in the code.
Teach the Impact Stuff
For Big Idea 5 (Impact of Computing), make flashcards with one real-world case each: algorithmic bias in hiring, open-source licensing, data privacy laws. Explain one to a friend weekly. If you can teach it, you own it.
Conclusion
The AP Computer Science Principles exam rewards preparation that is specific, not vague. You will not succeed by "being good at computers" — you will succeed by tracing logic cold, submitting the Create Task early, and treating the social implications of computing as real content, not filler. Learn the reference sheet's layout, run the clock on practice, and aim for the 4 or 5 with intent. The test is predictable; your study plan should be too.
