Skip to main content

🎓 Lesson 3: All-New vs Classic — Choosing Your Path

Lesson 1 introduced the two Captivates. Now let's turn that overview into a decision you can make in seconds. The rule is simpler than it looks: the all-new Adobe Captivate is your default for everything new, and Captivate Classic is the specialist you reach for in a handful of specific situations. This lesson gives you a decision tree you'll actually use.

📚 What You'll Learn

By the end of this lesson, you will be able to:

  • Apply a clear default rule: All-New for anything new, especially responsive courses
  • Name the specific situations where Classic is still the right call today
  • Tell the file formats apart — .cpt (all-new) vs .cptx (Classic) — and why an inherited file drives the choice
  • Walk a real project through a decision tree and land on the right tool
  • Understand why this choice is never permanent — you have both, and features keep moving into the all-new tool

⏱️ Estimated Time: 30 minutes

🎯 Project: Classify several sample project scenarios as all-new or Classic and justify each — then classify your own capstone idea. No software needed.

In This Lesson

🧭 The Default: All-New Wins by Default

Start every project by assuming you'll use the all-new Adobe Captivate All-New. It's the tool Adobe is actively building forward, it produces modern responsive courses that look right on any screen with little effort, and its block/component model is faster and friendlier for most work. Unless something specific pushes you toward Classic, the answer is the all-new tool. That's not a cop-out — it's the honest default that professional teams are converging on.

Why lead with a default at all? Because "which tool?" is the kind of question that can stall a beginner for an afternoon. Give yourself a strong starting assumption and you only have to justify the exception, not the whole decision every time. So: all-new unless proven otherwise.

🧠 Mindset

You might worry about "picking wrong" and wasting effort. Relax — you own both tools, the concepts transfer between them, and most real choices are obvious once you know the four exceptions below. This is a decision you'll make in seconds, not a fork in your career. If you're ever unsure, default to all-new and keep moving; movement teaches you more than deliberation.

The one file-format fact to anchor here: the all-new tool saves .cpt files, and Classic saves .cptx files. They are not interchangeable — a Classic .cptx doesn't open in the all-new tool as a native project. That single fact drives one of the biggest reasons to use Classic, which is next.

🗂️ The Four Reasons to Choose Classic

There are really only four reasons to override the default and open Captivate Classic Classic. If none of them apply, you're building in the all-new tool.

Reason What it looks like Why Classic
1. You inherited a .cptx A colleague hands you an existing Classic project to update The .cptx opens natively in Classic; editing it there avoids a risky rebuild
2. You need a Classic-only feature today Fluid boxes, advanced/conditional actions with variables at depth, VR/360, PowerPoint import, deep random question pools These are mature in Classic; some are still arriving in the all-new tool
3. Your team or standard requires it Your org's templates, review process, or shared library are all built in Classic Consistency with the team beats going solo in a different tool
4. A specific deliverable demands it A client explicitly asks for a VR/360 experience or a source .cptx The requirement itself names a Classic capability or file type

Notice the pattern: Classic wins when something outside your control names it — an existing file, a specific power feature, a team standard, or a client requirement. When the choice is genuinely yours and the project is new, the all-new tool is the better home.

💡 About those "Classic-only" features. This list is a snapshot, not a law. Adobe keeps moving capabilities into the all-new Captivate release by release, and there's ongoing work on importing Classic projects (often labeled beta). So treat feature-based reasons as "check the current version first" — something that was Classic-only last year may be in the all-new tool today. When a feature decision matters, verify against your installed version rather than any tutorial.

⚠️ Don't choose Classic out of habit or fear

The two weakest reasons to pick Classic are "it's what I saw in an old tutorial" and "I'm nervous about the new one." Old tutorials are everywhere because Classic has existed for years — that's history, not a recommendation. And the all-new tool is genuinely easier for most work once you start. If your only reason is habit or nerves, that's a signal to build in the all-new tool.

🌳 The Decision Tree

Here's the whole choice as a flow you can run in your head. Start at the top with any project and follow the arrows — most new work reaches "All-New" in one or two steps:

graph TD A["📁 A project lands on your desk"] --> B{"Are you handed an
existing .cptx file?"} B -->|Yes| C["🗂️ Use Captivate Classic
(edit it where it lives)"] B -->|No| D{"Does it truly need a
Classic-only feature today?
(VR/360, fluid boxes,
deep variables/actions)"} D -->|Yes, verified| C D -->|No| E{"Does your team or client
require Classic?"} E -->|Yes| C E -->|No| F["✨ Use the all-new
Adobe Captivate"] style A fill:#c7d2fe,color:#1e293b style B fill:#fde68a,color:#1e293b style D fill:#fde68a,color:#1e293b style E fill:#fde68a,color:#1e293b style C fill:#fed7aa,color:#1e293b style F fill:#bbf7d0,color:#1e293b

Figure 1 — The all-new vs Classic decision tree. Every path that isn't an explicit reason for Classic lands on the all-new tool.

Run a couple of examples through it. "A brand-new responsive onboarding course for phones and desktops" — no inherited file, no Classic-only feature, no team mandate — lands on all-new immediately. "Update last year's compliance module that exists as a .cptx" stops at the very first question: it's an inherited Classic file, so Classic. "A guided VR walkthrough of a facility" reaches the feature question and, because immersive VR/360 is a Classic strength today, lands on Classic — after you verify your version can't do it in the all-new tool yet.

✅ The 10-second version

New project, no Classic file, no Classic-only feature, no team mandate → all-new. Everything else → check Classic. That's the entire decision.

🔄 It's Not Either-Or Forever

The most freeing thing about this whole topic: you have both tools, so the choice is never permanent and rarely high-stakes. One subscription (or trial) unlocks the all-new Captivate and Captivate Classic together Win + Mac. Picking one for a project doesn't lock you out of the other for the next one.

Two trends make the default lean harder toward the all-new tool over time:

  • Features keep migrating. Each all-new Captivate release tends to absorb more of what used to be Classic-only. The gap narrows steadily, so your list of "reasons to use Classic" gets shorter, not longer.
  • Classic-project import is improving. Adobe has been working on ways to bring Classic projects into the all-new tool (often in beta). It's not a magic one-click for everything yet, so verify before you rely on it — but the direction is clear.

The practical upshot for your learning: invest your energy in the all-new tool (Parts 2, 3, and 5 of this course), and treat Classic as a well-understood specialist you can recognize and navigate when a project calls for it (Part 4's survey). Your skills transfer either way — a state is a state, a quiz is a quiz, a published course is a published course, whichever tool built it.

💡 A note on job listings

You'll still see "Captivate" (often meaning Classic, because it's been around longer) on plenty of job posts. That's exactly why this course surveys Classic honestly in Part 4 — so you can walk into an inherited .cptx and not blink. Knowing both, and knowing when to use each, is the marketable skill.

🎯 Try It: Classify These Projects

🏋️ Activity: Run the tree on real scenarios (no software)

Objective: Make the decision tree automatic by walking real projects through it — then apply it to your own course idea.

Steps

  1. For each scenario below, decide all-new or Classic, and write one sentence of justification (which branch of the tree it hit): (⏱️ 6 min)
    • A. A new, responsive customer-service course for staff who use phones and laptops.
    • B. Your manager forwards last year's safety course as a .cptx and asks for edits.
    • C. A 360° virtual tour of a warehouse with clickable hotspots.
    • D. A quick 5-slide knowledge check you're building from scratch this afternoon.
  2. Now take your own capstone topic (from Lesson 1's journal) and run it through the tree. Which tool? Why? (⏱️ 3 min)
  3. Write your answer to this: "If someone challenged my choice, the one fact that settles it is ______." (⏱️ 2 min)
💡 Hint (check your answers)

A — All-new (new + responsive, no Classic trigger). B — Classic (inherited .cptx, stops at question one). C — Classic (VR/360 is a Classic strength today — verify your version first). D — All-new (new, no trigger; speed favors the modern tool). For your capstone, it should almost certainly be all-new — that's the path this course builds.

✅ Activity Complete When…

  • You classified all four scenarios and named the deciding branch for each
  • You decided which tool your own capstone uses (it should be the all-new Captivate)
  • You can state the single fact that settles a tool choice for any project

🎯 Quick Quiz

Question 1: You're starting a brand-new responsive course from scratch, with no inherited file and no special feature needs. Which tool should you default to?

Question 2: Which of these is a genuine reason to choose Captivate Classic for a project today?

📓 Learning Journal

Start your Learning Journal today — a note in your favorite app, a doc, or a paper notebook. It's where you turn "I read that" into "I can do that." After each lesson, jot down:

  • Key concepts you learned
  • Things that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try
  • Your progress and how you feel about learning this

✍️ This lesson's prompt: Write down which tool your capstone course will use and the one reason that decides it. Then note one Classic-only feature you'd like to keep an eye on to see if it lands in the all-new tool later.

📝 Lesson Summary

🎓 Key Takeaways

  • Default to the all-new Adobe Captivate for anything new, especially responsive courses. You only override that default for a reason.
  • Choose Classic for one of four triggers: an inherited .cptx, a verified Classic-only feature, a team/standard requirement, or a deliverable that names a Classic capability.
  • File formats matter: .cpt (all-new) vs .cptx (Classic) aren't interchangeable, which is why inherited files drive the choice.
  • It's never either-or forever — you own both, and features keep migrating into the all-new tool, so re-check each release.

🎉 What You've Accomplished

You started with a fuzzy "two tools, which one?" and you leave with a decision tree you can run in ten seconds — plus a clear-eyed view that the choice is low-stakes because you own both. That confidence is exactly what keeps beginners from stalling. Well done.

❓ Common Questions at This Stage

If features keep moving to the all-new tool, will Classic disappear?

We won't predict Adobe's roadmap. What's true today: both ship together, Classic still holds some features the all-new tool is catching up on, and there's active work to import Classic projects. Learn the all-new tool as your primary skill and keep Classic in your back pocket — that's the durable strategy regardless of what changes.

Can I open a .cptx in the all-new Captivate?

Not as a native project — the formats are different. Adobe has been building import paths for Classic projects (often in beta), but don't assume a clean one-click conversion. If you're handed a .cptx, the safe move is to edit it in Classic. Check your current version to see what import is available.

I still feel nervous about the new tool. Should I just use Classic?

Nerves aren't a reason to choose Classic — and the all-new tool is genuinely friendlier once you start building in Lesson 5. Push through the nerves in the tool this course is built around; you'll be surprised how quickly it clicks.

🔭 Looking Ahead

In Lesson 4, you'll step away from the tool entirely and learn to think like a course designer — audience, measurable objectives, and a simple storyboard — the planning that makes a course actually teach.

✅ Before the Next Lesson

  • Confirm which tool your capstone will use (it should be the all-new Captivate)
  • Write this lesson's journal entry — your choice and the deciding reason
  • Keep your planned Lesson-5 trial-start date in view

📚 Additional Resources

🌟 Encouragement for the Journey

The best course authors aren't the ones who agonize over tool choices — they're the ones who decide fast and get building. You now decide fast. That's a professional habit, and you just picked it up in thirty minutes. Onward to design.