Version history that remembers the draft you sent your advisor
Save named versions at the moments that matter, compare any two side by side as code or as a rendered PDF, and restore an old version without losing the new one.

thesis_final.tex. thesis_final_v2.tex. thesis_final_v2_REVIEWED.tex. thesis_FINAL_actually.tex.
Everyone has a folder like this. It exists because you need to get back to a specific moment ("the version I sent to the committee") and file names are the only tool you have.
Luzbase gives you a better one.
Saving happens all the time. Versions happen on purpose.
Every keystroke in Luzbase is saved as you go, so you never lose work to a closed tab. That's different from a version.
A version is a named snapshot you create when something worth remembering happens. Press ⌘S (or Ctrl+S), or click Save version, and describe it in a few words:
- Sent to advisor
- Submitted to ICML
- Camera-ready
- Before cutting the related-work section
That description is the name you'll look for in six months, so write it for your future self.
Compare any two versions, two ways
Open History, pick a version and click Compare…. You get two views:
- Code diff: the LaTeX, line by line, with additions and removals highlighted. Best when you need to see exactly which
\citemoved. - PDF: a rendered, word-level comparison of the output. Best for your supervisor, who wants to know what changed in the argument, not in the markup.
This is how you answer the reviewer who asks "what did you change since the last round?" Compare Submitted against Revision 1 and you have the list.
Restore without fear
Found a paragraph you cut three weeks ago and now want back? Choose Restore this version → Restore as new version. Luzbase doesn't rewind the project and throw away everything since. It adds the old content as a new version on top, so the history stays complete and you can change your mind again.
If you only want to try an old idea, click Start a branch from this version instead. You can work on the old draft without touching the current one.
History per branch, notes per version
Each branch has its own history, so experiments on a branch don't clutter the main timeline. You can also leave a note on any version ("Advisor's comments are in the PDF she emailed on 3 March") to give context to whoever looks next.
How far back you can go
The Free plan shows the last 30 days of versions, which covers most papers during active writing. Pro keeps the full history, which matters for a thesis that runs for years or a paper that comes back from review eight months later.
The habit to build
Save a version every time the paper leaves your hands: to a co-author, an advisor, a journal or a conference. It takes three seconds, and it's the difference between "I think it was the version from around March" and an exact answer.
Start writing free and save your first named version today.



