Fix Blurry Text in Adobe Captivate Classic

Blurry text in Captivate Classic

If you’re developing eLearning with Adobe Captivate Classic, take a close look at the text in your published HTML5 output.

Does it look just a little out of focus?

That’s the best way I can describe the problem. The text isn’t so blurry that it’s unreadable. In fact, you might not notice the problem immediately. But compare the published text with properly rendered browser text and the difference becomes obvious. Captivate Classic’s text can look slightly soft or fuzzy.

Here’s a simple slide created in Captivate Classic.

Text on a white background discussing a font test and its clarity.

And here is how the text previews. Notice that the font is slightly out of focus.

A font test image with blue text asking if the text looks blurry, discussing how variable forces affect text sharpness.

I’ve confirmed the issue with Captivate Classic 11.8.3.8, and after quite a bit of testing, I’ve also confirmed two ways to deal with it.

First, It’s Not Your Project Resolution

One of the first things I suspected was project size.

My original project was 1024 x 768. That’s an older project size, so I wondered whether scaling the project on today’s larger displays was responsible for the slightly out-of-focus text.

I resized the project to 1280 x 720.

It made no difference.

I also created a brand-new Captivate Classic project containing a single slide with simple Arial text.

The published text was still slightly out of focus.

So let’s get this out of the way:

This problem has nothing to do with your Captivate project dimensions or resolution.

Changing a 1024 x 768 project to 1280 x 720, 1920 x 1080, or some other resolution isn’t the solution.

I also tested Scalable HTML Content, both enabled and disabled. That didn’t solve the problem either.

The issue followed the published content across different computers, browsers, operating systems, an LMS, and SCORM Cloud.

Solution #1: Upgrade the Project to Adobe Captivate 13.1 or Newer

This is my number-one recommendation.

If possible, upgrade your Captivate Classic project to Adobe Captivate 13.1 or newer.

I tested the same content after upgrading it to the new Captivate and confirmed that the slightly out-of-focus text problem goes away.

The text renders crisp and sharp.

If you’re maintaining an older Captivate Classic course and the project can be successfully upgraded, this is the solution I’d choose.

Of course, depending on the complexity of your Classic project, upgrading may not always be practical. Classic has features and workflows that don’t necessarily translate perfectly to the new Captivate.

Fortunately, if you need to remain in Classic, I found a workaround.

Solution #2: Add a Blank Variable to the Text

This one surprised me.

Create a user variable in Captivate Classic. For example:

vBlurry

Leave its value blank.

User variable input form with fields for type, name, value, and description.

Next, insert the variable reference into a Smart Shape containing text:

Insert Variable dialog box featuring options for variable type, view, and maximum length settings.
Image showing a text sample with the message 'This is a font test' in blue font against a white background, followed by a question about blurriness and an explanation about text rendering.

Preview the project again.

In my testing, the difference was immediate. The text that previously looked slightly out of looked better.

A text slide titled 'This is a font test' with additional text discussing blurriness and rendering sharpness.

Because vBlurry contains no value, learners don’t see anything extra. The variable simply sits invisibly inside the text.

There’s an Important Catch

Unfortunately, you cannot add $$vBlurry$$ once to a slide and fix every text object on that slide. The variable reference has to be included in each affected text object. For example, if a slide contains five Smart Shapes with text, adding $$vBlurry$$ to one Smart Shape fixes the rendering of that Smart Shape. The other four are unaffected.

Putting the variable in a separate object on the slide doesn’t fix the other objects, either. Nor can you simply put it on a Master Slide and expect all of the project’s text to become sharp.

That’s obviously not an appealing workaround if you have a large Captivate Classic project containing hundreds of text objects. It’s also why upgrading the project to Adobe Captivate 13.1 or newer remains my first recommendation.

Why Does Adding a Variable Work?

The behavior suggests that Captivate Classic uses a different rendering method when an object contains dynamic text.

With ordinary static text, Captivate Classic’s HTML5 output can make the characters appear slightly soft or out of focus.

Add a variable, however, and Captivate has to account for the possibility that the text could change while the course is running. That appears to cause Captivate to render the text differently.

The result is noticeably sharper text.

I want to emphasize that this is an explanation based on the behavior I’ve observed rather than documentation from Adobe. What I can confirm is the result: adding the variable fixes the problem in my testing.

Looking for Captivate training, mentoring, or support? I’ve got you covered!

Adobe: It’s Time to Deliver on the Captivate Promise

Adobe is taking forever to make the "new" Captivate equal to or better than Classic.

Back in July 2024, Adobe published the “New Captivate Roadmap,” outlining its vision for the future of the application. It was an encouraging post. Adobe acknowledged that the new Captivate didn’t yet match Captivate Classic and laid out a roadmap showing the missing features that would be added over time. Even more encouraging, the roadmap indicated that the journey to feature parity would be completed by 2025.

Well…

It’s almost 2027.

When Adobe introduced the all-new Captivate, I was cautiously optimistic.

I understood why the company chose not to simply modernize Captivate Classic. Starting with a new code base made sense. A modern architecture could provide a stronger foundation for the future, improve performance, simplify responsive authoring, and make it easier to add new capabilities over time.

What convinced many of us to stay invested wasn’t the initial release—it was Adobe’s promise. The published roadmap made it clear that the new Captivate would steadily evolve until it reached feature parity with Captivate Classic. The message was straightforward: Be patient. The features are coming.

So we waited.

Nearly three years later, Adobe has certainly made progress. The application has gained improvements to accessibility, AI-assisted content creation, responsive authoring enhancements, new widgets, and even a beta importer for Captivate Classic projects. Those additions are appreciated, and it’s obvious that work is being done.

The problem isn’t that Adobe isn’t developing Captivate.

The problem is how slowly it’s happening.

For developers who relied on Captivate Classic to build sophisticated software simulations, branching scenarios, variables, advanced actions, shared actions, object states, and the countless other features that made Captivate such a powerful authoring tool, the new version still feels unfinished. Every release seems to introduce one or two meaningful improvements while leaving a long list of highly requested capabilities untouched.

Take software simulations as an example. This was once Captivate’s signature feature, and it’s still nowhere near the level of Captivate Classic. During recording, the generated text instructions often require significant editing because they simply aren’t as accurate as they were in Classic. When the recording is complete, the cursor appears as a gray blob instead of an actual mouse pointer, forcing you to manually change its appearance. Even something as basic as formatting the instructional captions has become more tedious. In Classic, you could define object styles so every simulation caption looked exactly the way you wanted. Change the style once, and every caption updated automatically. In the new Captivate, you’re editing captions one at a time because there isn’t an equivalent way to globally control the appearance of simulation instructions. These aren’t flashy, headline-grabbing features—they’re the everyday workflow improvements that made Captivate such an efficient tool. Losing them doesn’t feel like progress. It feels like a step backward.

Still Waiting…

Here’s just a sampling of the capabilities that Captivate Classic users have been waiting to see fully realized:

  • A software simulation workflow that truly matches Classic.
  • Accurate simulation text instructions without extensive cleanup.
  • Proper mouse pointers during simulation recording instead of generic cursor graphics.
  • Global styling for simulation captions rather than editing them one at a time.
  • Full parity for advanced actions and shared actions.
  • More complete variable support.
  • Virtual reality/360 images.
  • MS Word round-tripping.
  • Video demo mode.
  • Export as a PDF.
  • An asset library that isn’t a joke (seriously, there are a few hundred assets included with Captivate when there should be millions).
  • A faster release cadence that gives users confidence the platform is actively evolving. (It feels like Adobe isn’t truly supporting eLearning or technical communications any longer.)

This isn’t an exhaustive list. Ask ten experienced Captivate developers what they’re still missing, and you’ll probably get ten different answers. But you’ll also find remarkable agreement on one thing: we’re still waiting for the application Adobe promised.

That’s disappointing because Adobe set the expectation that the new Captivate would eventually stand shoulder to shoulder with Classic. According to the roadmap, much of that work was expected to be complete by 2025. At the current pace, that goal feels increasingly distant.

Meanwhile, the rest of the industry isn’t standing still. Organizations need to choose authoring tools today, not several years from now. Consultants have client deadlines. Corporate training teams have projects to deliver. Colleges need software they can confidently teach. Every month that passes without substantial progress gives organizations another reason to evaluate alternatives.

Articulate, for example, has established a steady release cadence for Storyline 360, rolling out new features, enhancements, and bug fixes almost every month. Not every update is groundbreaking, but the cumulative effect is significant. Users know the product is actively evolving, and they rarely have to wait long to see improvements or requested capabilities. That’s the kind of momentum Captivate once had—and it’s the kind of momentum Adobe needs to regain if it expects long-time Captivate users to remain invested.

Many long-time Captivate users have already transitioned to Storyline, while others are exploring other authoring platforms. The conversations I have with clients and fellow developers are no longer about when a feature will arrive—they’re about whether it ever will.

That’s the part that concerns me the most.

Adobe already knows what users are asking for. They published the roadmap. They acknowledged the missing functionality. They assured customers that feature parity with Classic was the destination. That roadmap generated excitement because it suggested a clear path forward, not simply a new product with a different target audience.

Promises, however, eventually have an expiration date.

At some point, users stop asking what’s coming next and begin wondering whether the destination has quietly changed.

I’ve been teaching Captivate for decades. I’ve written books about it, trained thousands of developers, and recommended it to organizations around the world. Captivate wasn’t just another eLearning authoring tool—it was, for many years, the application that set the standard for software simulations and advanced interactive learning.

That’s why this isn’t written out of anger. It’s written out of disappointment.

I want Captivate to succeed.

Adobe has talented engineers, a loyal customer base, and one of the strongest brands in creative software. The new Captivate has enormous potential, but potential alone won’t convince organizations to stay with the platform. They need to see substantial progress, a faster release cadence, and visible movement toward the parity Adobe promised.

Personally, I’d love nothing more than to write an article praising Adobe for finally delivering the features we’ve been waiting for. I want to recommend Captivate without reservations the way I once did. But that will only happen if Adobe accelerates development and demonstrates that the roadmap published years ago is still the roadmap they’re committed to following.

Adobe didn’t promise a different Captivate. It promised a better Captivate—one that would eventually match and surpass Classic. Until software simulations and the everyday authoring experience reach that level, that promise remains unfulfilled.

So here’s my message to Adobe:

Come on.

It’s time to pick up the pace.

Your most loyal customers have been remarkably patient because they believed in your vision. But patience isn’t unlimited, and every slow release makes it a little harder to believe that Captivate Classic’s capabilities will ever fully arrive in the new Captivate.

The roadmap created hope.

Now it’s time to deliver on it.

Guide To Adobe Captivate Classic Fluid Boxes

If your Adobe Captivate Classic project looks clean on desktop but falls apart on a phone, this guide to Fluid Boxes will fix that fast.

Fluid Boxes are Captivate’s responsive layout system, and once you understand how containers, wrapping, and alignment work together, you can build slides that behave predictably instead of fighting you.

Start With A Responsive Project

Fluid Boxes only work in a responsive project. Open Captivate and create a Responsive Project, not a blank non-responsive project. If you already built slides in a non-responsive file, you cannot simply turn Fluid Boxes on later. You will need to rebuild those slides in a responsive project.

After the project opens, go to the first content slide and switch to the Fluid Boxes view if needed. Captivate may add Fluid Box placeholders automatically. Think of each box as a container that controls where objects can live and how they resize.

Build Your First Fluid Box Layout

Start simple. Insert a vertical parent Fluid Box so the slide is split into stacked sections, such as a header, content area, and footer. Then select the middle section and divide it into horizontal child Fluid Boxes if you want side-by-side content.

This parent-child structure matters. A parent box controls major layout areas. Child boxes control the objects inside those areas. If your slide gets messy, it is usually because too many objects were dropped into one box without a clear structure.

Add Content The Right Way

Drag text captions, images, and buttons into the correct Fluid Box, not just onto the slide. When the object is inside the box, Captivate highlights the container. That visual cue matters because objects that are not properly assigned may overlap or resize in unexpected ways.

Use one main object type per box when possible. For example, place a heading in one box and an image in another. You can mix objects, but dense boxes are harder to control on smaller screens.

Set Alignment And Distribution

Select a Fluid Box and use the Properties Inspector to control alignment. You can center objects vertically or horizontally, justify them to edges, and adjust padding. Padding is one of the fastest ways to make a slide look professional because it keeps content from touching box edges.

If objects appear cramped, increase padding before changing object sizes. If objects are unevenly spaced, check the distribution setting for the box instead of manually moving items. Manual positioning works against the Fluid Box system.

Control Resizing And Wrapping

Here is the part most developers miss in a guide to Captivate Fluid Boxes: wrapping controls responsiveness more than object size does. Select the Fluid Box and decide whether objects should wrap to the next line as the screen narrows. Wrapping is useful for groups of images or buttons. If wrapping is off, objects keep trying to fit on one line and may become too small.

Also review whether an object can grow or shrink. For logos and icons, lock the aspect ratio so they do not distort. For text-heavy captions, allow enough space for expansion. A layout that works on desktop can break on mobile if the text box cannot adapt.

Use Static Fluid Boxes When Needed

Not every object should resize. If you have a banner, logo area, or navigation strip that should keep its shape, consider setting that box to Static. A static box gives you more control, but there is a trade-off. Too many static boxes reduce flexibility on smaller screens.

Use static boxes only when consistency matters more than adaptability. For most body content, regular responsive Fluid Boxes are the better choice.

Preview Before You Keep Building

Preview early, not after ten finished slides. Use the device preview options and test desktop, tablet, and phone sizes. Watch for three common issues: text that wraps awkwardly, images that scale too aggressively, and stacked objects that become too tall.

When something fails, fix the container first. Most layout problems are caused by the box settings, not the object itself.

Troubleshoot Common Fluid Box Problems

If objects overlap, confirm they are inside separate boxes or that wrapping is enabled. If text is cut off, allow the caption more vertical space or reduce the amount of text. If a slide feels unstable across devices, simplify the hierarchy by using fewer nested boxes.

A good rule is to build the slide in broad regions first, then place content, then test responsiveness. That order saves time and gives you a layout you can trust.

Fluid Boxes work best when you stop treating slides like fixed-position canvases. Build with containers, test often, and let the layout system do its job. That is how you create responsive projects that hold up under real-world pressure.

Copy Lessons Between Articulate Rise Courses in Seconds

Need to reuse a lesson you’ve already created? Instead of rebuilding it from scratch, copy the entire lesson to another Rise course in just a few clicks.

If you develop Articulate Rise courses regularly, chances are you’ve created lessons that you’d like to reuse. Maybe it’s a course introduction, a knowledge check, a company policy, or a standard resources page.

While you could recreate the lesson—or even copy blocks one at a time—there’s a much faster option. Rise lets you copy an entire lesson from one course to another, preserving all of the text, images, interactions, and formatting.

It’s a simple feature that can save a tremendous amount of development time.

Why Copy Lessons?

Copying an entire lesson is ideal when you have content that appears in multiple courses, such as:

  • Course introductions
  • Learning objectives
  • Navigation instructions
  • Accessibility information
  • Knowledge checks
  • Company policies
  • Resource pages
  • Contact information
  • Course conclusion pages

Instead of rebuilding these lessons each time, copy them and make any minor edits needed for the new course.

How to Copy a Lesson to Another Course

Copying a lesson takes less than a minute.

  1. Locate the lesson you want to copy.
  2. Click the three-dot menu next to the lesson.
  3. Choose Copy to Another Course.
  4. Select the destination course.
  5. Open the destination course.
  6. Drag the copied lesson to its desired location in the course outline.
A user interface showing 'Training Objectives' with options to change the icon, duplicate, copy to another course, or delete the lesson.

That’s all there is to it.

What Gets Copied?

When you copy a lesson, Rise copies everything in it, including:

  • Text
  • Images
  • Videos
  • Interactive blocks
  • Knowledge checks
  • Buttons
  • Flashcards
  • Labeled graphics
  • Accordions
  • Process interactions
  • Formatting

The copied lesson becomes part of the destination course, so you can edit it without affecting the original.

Create Your Own Lesson Library

Here’s a productivity tip: create a dedicated Rise course that serves as your personal lesson library.

Populate it with lessons you use repeatedly, such as:

  • Welcome pages
  • Course introductions
  • Learning objectives
  • Navigation instructions
  • Accessibility information
  • Frequently used interactions
  • Knowledge checks
  • Resource pages
  • Course conclusion pages

When you begin a new project, simply copy the lessons you need into the new course and arrange them as desired. Over time, you’ll build a library of polished, reusable content that can dramatically speed up course development.

Final Thoughts

Copying lessons between Rise courses is one of the easiest ways to eliminate repetitive development work. Instead of recreating an entire lesson—or copying assets one at a time—you can move complete lessons into another course in seconds.

If you routinely build multiple Rise courses, this feature is well worth adding to your workflow. You’ll spend less time rebuilding content and more time creating engaging, effective learning experiences.

Rise Training

If you need to learn Rise fast, check out my 2-hour virtual instructor-led Rise class.

Where Did the Camtasia Library Assets Go? (And How to Restore Them in Minutes)

Cmtasia library assets are missing

If you’ve just installed TechSmith Camtasia 2026 and opened the Library panel expecting to see all of the familiar lower thirds, intros, icons, motion graphics, and other built-in assets, you’re probably wondering what happened.

Don’t worry—you aren’t missing anything, and your installation isn’t broken.

Beginning with Camtasia 2026, TechSmith no longer installs the default library assets with the application. While this may come as a surprise to longtime users, the change was intentional. Better yet, if you prefer the classic library from Camtasia 2025, you can download it for free and add it to Camtasia 2026 in just a few minutes.

Why TechSmith Removed the Default Library

According to TechSmith, there were several reasons behind this change:

  • Smaller downloads and faster installation. Without hundreds of bundled assets, Camtasia downloads and installs more quickly while consuming less disk space.
  • More flexibility. TechSmith is encouraging users to leverage the online Assets service, where content can be updated and expanded without requiring a new version of Camtasia.
  • A cleaner Library panel. Rather than filling the Library with stock content, TechSmith now views it as a place to store your own reusable assets—logos, titles, animations, lower thirds, callouts, and other items you use repeatedly.

It’s a reasonable approach. After all, many experienced Camtasia users eventually build a personal library of assets that reflects their organization’s branding and production style.

However, many trainers, instructional designers, and video creators have grown accustomed to the built-in library over the years. Fortunately, TechSmith anticipated that concern.

Restore the Camtasia 2025 Library

TechSmith is making the complete Camtasia 2025 Library Assets available as a free download. If you’d like your familiar collection of intros, lower thirds, icons, animations, and motion graphics back, simply visit the following TechSmith support page:

https://support.techsmith.com/hc/en-us/articles/41310557595917-Where-are-the-Camtasia-Library-Assets

The support article explains the change and includes a direct download for the Camtasia 2025 Library Assets package.

After downloading the library package, importing it into Camtasia 2026 takes less than a minute.

Import the Library into Camtasia 2026

  1. Download the Camtasia 2025 Library Assets from the TechSmith support page.
  2. Open Camtasia 2026.
  3. Choose File > Library > Import Zipped Library.
  4. Browse to the downloaded .libzip file.
  5. Select whether to create a new library or merge the assets into an existing one.

That’s it! The familiar library assets are immediately available for use in your projects.

Want to Learn Camtasia?

If you’re looking to sharpen your Camtasia skills, check out my live online TechSmith Camtasia Certificate Course. Across three hands-on sessions, you’ll learn how to confidently record, edit, enhance, and publish professional-quality videos. Every student receives a copy of my TechSmith Camtasia: The Essentials workbook, access to the class recordings, and an IconLogic Certificate of Completion.

Learn more here:

https://www.iconlogic.com/instructor-led-training/software-title/camtasia.html

My Take

Personally, I understand why TechSmith made this change. Removing hundreds of bundled assets results in a smaller installation and allows the company to keep its online Assets library fresh without requiring software updates.

That said, I also appreciate that TechSmith didn’t simply eliminate the legacy library. Providing the complete Camtasia 2025 assets as a free download is a thoughtful compromise. Existing users can continue working with the assets they’ve come to know, while new users begin with a clean Library that’s ready to hold their own reusable content.

So, if you install Camtasia 2026 and think your Library is missing, don’t panic. It’s simply a new approach. And if you miss the classic assets, restoring them takes only a few clicks.

Happy recording!

Introducing “Be the Best Trainer You Know”

Kevin teaching a virtual class from his home office.

Over the past 30 years, I’ve taught thousands of learners in classrooms, virtual classrooms, conference centers, hotel meeting rooms, home offices, and more than a few places where professional training probably shouldn’t have happened.

Along the way, I’ve discovered that great training has surprisingly little to do with being the smartest person in the room.

Expertise matters, of course. But expertise alone doesn’t create engagement, participation, or lasting learning.

An illustrated owl wearing headphones is seated at a desk with a laptop displaying a grid of icons, a coffee mug, and a notebook, promoting virtual training.

That’s why I wrote Be the Best Trainer You Know: When Expertise Meets Engagement—How to Deliver Virtual Training That Learners Remember.

This isn’t a book about technology. It isn’t a guide to Microsoft Teams, Zoom, Webex, or any other platform. Those tools will continue to evolve.

Instead, this book focuses on the skills that never go out of style.

Inside, you’ll learn practical techniques for:

  • Designing engaging virtual learning experiences
  • Building learner participation and interaction
  • Asking questions that spark discussion and critical thinking
  • Using polls, assessments, and activities effectively
  • Speaking confidently to a virtual audience
  • Creating visuals that support learning instead of distracting from it
  • Managing the technology behind the scenes
  • Holding attention and maintaining engagement throughout a session
  • Delivering training that learners actually remember

The strategies in this book are based on lessons learned from more than three decades in the classroom and more than twenty years teaching live online. Some lessons came from successes. Others came from mistakes. All of them helped shape the techniques I rely on today.

An informative graphic promoting a practical guide for becoming an engaging virtual trainer, featuring key techniques for effective online training and insights from expert Kevin Siegel.

You’ll also meet a few familiar characters along the way. An owl, a chicken, and more than a few foxes make appearances throughout the book. They occasionally help illustrate a point, lighten the mood, and remind us that learning doesn’t have to be boring.

My goal is simple: help you become the trainer people remember for the right reasons.

Whether you’re new to training or a seasoned professional looking to strengthen your virtual facilitation skills, you’ll find practical ideas that you can put to work immediately.

If you’ve ever wondered why some trainers seem to effortlessly engage an audience while others struggle to keep learners focused, this book shares the techniques that make the difference.

Teaching has been one of the great joys of my professional life. I hope the stories, lessons, and techniques collected in these pages help you grow your own skills, increase your confidence, and elevate the learning experiences you create for others.

After all, becoming the best trainer on your team starts with becoming the best trainer you know.

Why TechSmith Camtasia Hotspots Don’t Work After Uploading an MP4

User interacting with Camtasia Smart Player interface showing quizzes, hotspots, branching, and video controls

I recently received the following question from a Camtasia user:

"I developed a Camtasia project with interactive hotspots. This project is intended for upload in the original Blackboard LMS. I published the project using MP4 with Smart Player. The hot spots do not work when I upload the MP4 in Blackboard. Could you please provide advice on how to rectify this. Your help is much appreciated."

The issue is a common one, and the answer comes down to understanding how Camtasia interactivity actually works.

The MP4 Is Just a Video

Many Camtasia users assume that interactive hotspots are embedded directly into the MP4 video. Unfortunately, that’s not how Camtasia works.

An MP4 is simply a video file. It contains the audio and video, but not the programming required to support hotspots, quizzes, and other interactive features.

As a result, if you upload only the MP4 to Blackboard or another LMS, learners will see the video, but the hotspots won’t function.

Where the Interactivity Lives

The interactive features are provided by the web-based player that accompanies the video.

On Windows, Camtasia creates this player when you publish using MP4 with Smart Player. On Mac, it is created when you choose Export as Web Page.

In both cases, Camtasia generates an HTML page and several supporting files that work together to provide the interactivity. The MP4 is only one piece of the published output.

How to Make Hotspots Work

To preserve interactivity:

  1. Publish the project using MP4 with Smart Player (Windows) or Export as Web Page (Mac).
  2. Upload the entire published output folder to a web server.
  3. Direct learners to the generated HTML file rather than the MP4 video.

When learners launch the HTML page, Camtasia loads the player and supporting files that make the hotspots work.

Why Uploading Only the MP4 Fails

When you upload only the MP4, Blackboard treats it as a standard video file.

The LMS has no access to the HTML page, scripts, and supporting assets that define and control the hotspot behavior. Since those files are missing, the video plays normally, but the interactivity is lost.

What About Blackboard?

Whether this approach works directly within Blackboard depends on how your Blackboard environment is configured.

Some Blackboard installations allow web-based content packages to be uploaded and launched. Others are primarily designed to host videos and documents.

If Blackboard cannot host the published Camtasia package, you may need to place the published files on a web server and then provide learners with a link from within Blackboard.

The Bottom Line

If your Camtasia project contains hotspots, uploading only the MP4 is not enough.

The interactivity lives in the published web content generated by Camtasia, not in the video itself. To ensure hotspots function correctly, publish the project, upload the entire output package, and direct learners to the generated HTML page rather than the MP4 file.

Camtasia Training and Support

Need Camatasia support? Check out my Camtasia training and mentoring options.

Adobe Captivate: The Essentials & Beyond [2026 Edition] — Now Updated for 13.1

If you’re using the new version of Adobe Captivate, there’s good news.

The 2026 edition of Adobe Captivate: The Essentials and Beyond has just been updated to include the latest Captivate 13.1 enhancements—so you can stay current without guessing what’s changed or how to use it.

Book cover for 'Adobe Captivate: The Essentials & Beyond' featuring a kitten playing with a green ball marked 'Cp'. The background is a solid light green.

What’s New in This Update?

The updated book adds practical, hands-on content focused on features developers are asking about right now:

Upgrade Your Classic Projects
If you’ve got legacy content, you don’t have to start over. New lessons walk you through how to bring Captivate Classic projects into the new Captivate, so you can reuse what you’ve already built and modernize your workflow.

Master the New Slider Widget
The slider widget opens the door to interactive surveys and learner input. The new content shows you exactly how it works, how to configure it, and how to use it effectively in real-world projects.

Bonus: Branding Blocks Activities
Consistency matters. The book now includes bonus, hands-on activities that teach you how to use branding blocks to add headers, footers, and a polished, consistent look across your project.

Same Project-Based Learning—With the Latest Features Built In

If you’ve used my books before, you know the approach:
no fluff, no theory overload—just step-by-step, project-based learning.

You’ll still build a complete, real-world project from the ground up while learning how the new features fit into your workflow. The difference is that now, everything is aligned with Captivate 13.1.

To learn more or purchase the book, click or tap here.

Articulate Storyline 360: The Essentials & Beyond [2026 Edition]—The Hands-On Workbook to Build Real eLearning Skills

If you’ve ever opened Articulate Storyline 360 and wondered where to start, the issue isn’t the software—it’s the lack of a clear path.

Random tutorials don’t build real skill.
Building does.

That’s exactly what Articulate Storyline 360: The Essentials & Beyond is designed to fix.

👉 Get the book: https://www.iconlogic.com/articulate-storyline-360.html

A cute golden retriever puppy holding a blue and orange chew toy labeled 'Storyline' in its mouth, with a purple background featuring the title 'Articulate Storyline 360: The Essentials and Beyond' and author names.

Build—Don’t Just Follow Along

This is a hands-on workbook, not a reference guide.

You’ll:

  • Start by exploring a completed project (see how it all fits)
  • Build your own course step by step
  • Reinforce skills with guided activities and confidence checks

No fluff. No disconnected features. Just real development.

What You’ll Learn

You won’t just click buttons—you’ll understand how to create working eLearning.

  • Slides, layers, states, and triggers
  • Drag-and-drop and branching scenarios
  • Variables and conditional logic
  • Quizzes that go beyond basic recall
  • AI features that speed up development
  • Accessibility best practices

Everything ties together into projects you can actually use.

Built for Real-World Skills

This workbook is designed the way people actually learn:

  • Step-by-step, hands-on instruction
  • Real projects—not throwaway exercises
  • Minimal theory, maximum application

Whether you’re new or leveling up, you’ll leave with usable skills—not just notes.

Become the Go-To Developer

Teams don’t need someone who “knows Storyline.”
They need someone who can build.

This workbook helps you:

  • Turn content into engaging eLearning
  • Solve problems independently
  • Build faster and more confidently

That’s how you become the person your team relies on.

Get Started

All you need:

  • The workbook
  • A trial or subscription to Articulate 360
  • A willingness to build as you learn

No experience required.

This isn’t just another book.
It’s your step-by-step path to building real eLearning—and becoming indispensable.

Upgrade to the New Adobe Captivate: Reuse Your Captivate Classic Projects Without Rebuilds

Comparison of Classic Captivate 2019 and New Captivate interfaces showing faster progress and time saved.

You’ve already built the project. The question is: can you use it in Captivate 13.1 without rebuilding everything?

The short answer: yes—but expect some cleanup.

If you’re importing Adobe Captivate Classic (CpC) projects into Captivate 13.1, two things will almost always need your attention: click boxes and fonts. Handle those correctly, and you’ll save hours (or days) of redevelopment.

What to Expect During Import

The import process itself is straightforward. Open Captivate 13.1 and import your CpC project.

Here’s what typically comes through without issue:

  • Slide structure
  • Images and most visual assets
  • Text content (though not always styled correctly)

Where things get challenging is interactivity and formatting.

Fix #1: Replacing Click Box Functionality

Click boxes don’t translate cleanly into Captivate 13.1. After import, you may notice:

  • Interactions that no longer respond
  • Navigation that’s broken
  • Invisible or non-functional clickable areas

The Fix

Rebuild those interactions using supported objects:

  • Replace click boxes with buttons or interactive components
  • Reassign actions (Next Slide, Jump to Slide, Show/Hide, etc.)
  • Reconnect any logic tied to the original interaction

This step is manual, but it’s also a chance to simplify and modernize your design.

Fix #2: Updating Fonts Project-Wide

Font issues are common after import and can make your project look inconsistent.

What You’ll See

  • Fonts that don’t work as expected
  • Mismatched text styles
  • Layout shifts caused by font changes

The Fix

Update fonts globally instead of slide by slide:

  • Select a standard font for the project
  • Apply it across all slides
  • Review headings, captions, and interactive text for consistency

A quick global update can dramatically improve the final look.

Want to see the process?

Here’s a YouTube video that demonstrates the import process from Adobe Captivate Classic to Adobe Captivate.

Bottom Line

You don’t need to rebuild your Captivate Classic projects from scratch—but you do need a plan.

Focus on:

  • Replacing click box interactions
  • Standardizing fonts

Do that, and your legacy content can transition cleanly into Captivate 13.1.

Ready to Work Faster in Captivate?

If you’re using Captivate regularly, hands-on training can dramatically shorten your development time and improve your output.

👉 Explore Adobe Captivate training from IconLogic:
https://www.iconlogic.com/instructor-led-training/software-title/captivate.html