Overview
Daniel Scott
Founder of Bring Your Own Laptop & Chief Instructor
instructorI discovered the world of design as an art student when I stumbled upon a lab full of green & blue iMac G3’s. My initial curiosity around using the computer to create ‘art’ developed into a full-blown passion, eventually leading me to become a digital designer and founder of Bring Your Own Laptop.
Sharing and teaching are a huge part of who I am. As a certified Adobe instructor, I've had the honor of winning multiple Adobe teaching awards at their annual MAX conference. I see Bring Your Own Laptop as the supportive community I wished for when I was first starting out and intimidated by design. Through teaching, I hope to bring others along for the ride and empower my students to bring their stories, labors of love, and art into the world.
True to my Kiwi roots, I've lived in many places, and currently, I reside in Ireland with my wife and kids.
We’re awarding certificates for this course!
Check out the How to earn your certificate video for instructions on how to earn yours and click the available certificate levels below for more information.
History is a temporary, session-only list of your recent actions, basically a visual undo stack. Version History is the long-term lifesaver for cloud documents, letting you return to earlier saved versions later on, even after closing the file, especially if you mark key versions to keep.
Illustrator has two features with almost the same name, and they do very different jobs.
One is History. The other is Version History. If you mix them up, it is easy to assume your file is safely backed up when it is not. And if you know how they really work, you can stop making endless copies called things like final, final-v2, and final-final-really-this-one.
The better of the two, by far, is Version History. But there is a catch. It only works with cloud documents.
Version History tracks saved stages of your Illustrator file over time. If your document lives in the cloud, Illustrator quietly records versions as you work.
That means you can open the File menu, go into Version History, and see previous states of the document from earlier in the day or even much older points if you have kept them.
This is brilliant for those moments when you make a big change and then immediately regret it. You can simply jump back to a previous version and restore it.
It feels a bit like Undo, but much more powerful because it is not limited to the current editing session.
This is where Version History starts earning its keep because you can browse saved states of the document instead of guessing your way back.
Illustrator does not record every tiny move here as a separate permanent backup. Instead, it builds up versions of your document as you work and save.
So rather than storing every nudge and paste forever, it creates a timeline of useful checkpoints. That makes it much more practical for rolling back to earlier design decisions.
If you changed a font, altered a logo colour, removed a block of content, or explored a different direction, Version History gives you a way to return to those earlier stages without creating a completely separate file.
A lot of people still protect themselves by making duplicate files before every risky edit. The pattern usually looks something like this:
project.ai
project-v2.ai
project-v3.ai
project-final.ai
project-final-final.ai
It works, sort of. But it gets messy very quickly.
Version History is the cleaner way to handle that. Instead of creating another file every time you hit a fork in the road, you can keep working in the same cloud document and deliberately save meaningful checkpoints inside it.
This is the part that matters most.
Illustrator will keep building version entries as you work, but not all of them remain forever. Ordinary versions expire after 30 days. So if you want a version to stick around long term, you need to mark it.
Think of marked versions as bookmarks for major decisions.
If you are about to try a new font, remove a section, swap colours, or send something to a client, that is a good moment to mark the current version and give it a clear name.
Useful names might include:
Before font change
Client approved version
Deleted header section
Homepage concept A
The name is the real win here. A labelled version is far easier to return to than a vague time-based entry you have to guess at later.
A named checkpoint is much more useful than a mystery timestamp when you need to roll back weeks or months later.
You do not need to mark every tiny edit. That would just create clutter.
Mark a version when:
You are about to try a risky change
You have reached an approved milestone
You want to preserve an alternate concept
You are deleting or replacing something substantial
You know you may need to return to this exact state later
That is the sweet spot. Not every step. Just the meaningful ones.
One of the nicest things about Version History is that it lets you move back and forth.
You can restore an older version to see what the file looked like before a big decision. If that turns out to be the wrong move, you can still return to the more current version again.
So restoring an older version does not mean you are trapped there forever. It is much more forgiving than people expect.
That makes it ideal for experiments. You can try things, compare directions, and recover older ideas without spawning a dozen duplicate files.
If a document has been around for a while, Version History can get busy. Illustrator includes tools to make that easier to manage.
You can search for version names and filter what appears. That becomes especially handy if you have been disciplined about naming your marked versions properly.
A vague label like edit is not much help six months later. A label like green logo test or client amends round 2 is much easier to find.
If your Illustrator file is saved on your local hard drive as a regular .ai file, Version History will not be available.
That is the main limitation.
Cloud documents are easy to spot because Illustrator shows the cloud icon with the file. If the file is purely local, you will not get the same version-tracking system.
So if you open the file menu on a local document and wonder why Version History is unavailable, that is why.
If you want Version History, the file needs to live in the cloud first. Without that, the feature simply is not in play.
If you have a file sitting on your computer and want access to Version History, save it as a cloud document.
The exact layout varies a bit between Mac and PC, but the basic process is the same:
Open the local Illustrator file.
Go to File.
Choose Save As.
Select the option to save it to the cloud.
Once it becomes a cloud document, Version History starts working.
If you already spend most of your time in Illustrator, cloud documents are worth getting comfortable with. Aside from Version History, they make sharing and storage much easier.
Now for the other one.
History is not the same thing as Version History at all. It is closer to a visual list of your recent actions. You can think of it as a more transparent form of Undo and Redo.
It records all the little steps you take while working, such as:
Paste
Move
Scale
Clear
Transform actions
That can be helpful because you can see exactly what you have just done, rather than repeatedly pressing Undo and hoping you stop at the right point.
The History panel is handy for stepping through recent actions, but it is still just session-based undo with a nicer face.
The History panel has one big advantage.
It works even on non-cloud documents.
So if you are editing a regular local Illustrator file, History still gives you a visible list of recent actions while the file is open.
That makes it practical for short-term corrections during a live editing session.
Here is the problem.
Once you close the file, the History list is wiped. Even if you save first, closing and reopening the document clears that action history.
So if you make a mistake, save the file, close it, and only then realise what went wrong, History cannot help you. The undo trail is gone.
That is the exact moment where Version History becomes the hero, provided the file is a cloud document.
If you want the simplest possible distinction, it is this:
History is for recent actions in the current session.
Version History is for returning to earlier saved document states over time.
History disappears when the document is closed.
Version History survives closing and reopening, as long as the document is in the cloud.
History tracks tiny edits.
Version History is better for milestones and recovery.
You do not have to choose one forever. They are useful at different moments.
Use History while actively working when you need to step back through recent actions.
Use Version History when you want actual peace of mind. That is the one that helps after a file has been saved, closed, reopened, or heavily changed over time.
The best workflow is simple:
Work in a cloud document whenever possible.
Use History for quick short-term undo decisions.
Mark important versions whenever you reach a major milestone.
Give those marked versions useful names.
Stop creating endless duplicate files unless you genuinely need separate deliverables.
The easiest habit to build is this: whenever you are about to make a significant change, pause for two seconds and mark the current version.
That tiny step can save you from rebuilding work later, especially when you realise the older design was better, the client preferred the previous option, or you deleted something you suddenly need back.
And if you have ever had that horrible moment where you saved, closed the file, then remembered the one thing you forgot to undo, this is exactly the feature that gets you out of trouble.
No. Version History requires a cloud document. If the file is only stored locally on your hard drive, Illustrator will not provide that long-term version timeline.
Standard versions expire after 30 days. If you want a version to stay permanently, mark it and give it a name so it remains available later.
Pretty much, yes. It is a visible list of your recent actions, which makes undoing and redoing a bit easier to follow, but it is still temporary and session-based.
It clears out. Once the document is closed and reopened, that action-by-action history is gone, even if the file was saved.
For most in-progress design checkpoints, Version History is a cleaner option. You may still want separate files for final deliverables or major alternate outputs, but for normal revision safety, marked cloud versions are usually enough.