If you use Bluebeam Studio on a project team, you've hit the two-mode fork: do you start a Project or a Session? The short answer on Bluebeam project vs session is this, a Studio Project is a shared cloud folder for storing and version-controlling your documents over the long haul, while a Studio Session is a real-time collaborative markup space where several people redline the same PDF at once. They solve different problems, and the teams that get the most out of Studio use both together. Here's the plain explainer.

What a Studio Project actually is

Think of a Studio Project as a secure, cloud-hosted document repository that lives inside Bluebeam. It's where the authoritative copies of your drawings, specs, RFIs, and supporting files live for the duration of a job. The defining feature is check-in / check-out: when you check a file out, you lock it so no one else can edit it at the same time, you make your changes locally, then you check it back in as a new version.

  • Persistent storage, files stay in the Project until you remove them, often for the life of the job.
  • Version history, every check-in creates a tracked revision, so you can see who changed what and roll back if needed.
  • Access control, you invite specific members and set permissions per folder.
  • Folder structure, mirror your real project tree (Drawings, Specs, Submittals, etc.).

A Project is not a live editing room. Two people can't mark up the same checked-out file simultaneously. Its job is to be the single source of truth and to keep your document set organized and versioned.

What a Studio Session actually is

A Studio Session is the live one. You upload one or more PDFs into a Session, invite people, and everyone can add markups to the same document at the same time, and see each other's comments appear in near real time. It's the digital equivalent of a whole team standing around one printed sheet with their own pens.

  • Real-time co-markup, multiple reviewers annotate concurrently; changes sync as they happen.
  • Record / chat / activity log, every markup is attributed to a person and time-stamped, and there's a running comment feed.
  • Temporary by design, Sessions are meant to be opened for a review cycle and then finished.
  • Finish & export, when the review is done, you "Finish" the Session and pull the marked-up file back out (often straight back into a Project).

A Session is great for review meetings, coordination markups, and punch lists. It is not where you want documents to live permanently, it has no real folder hierarchy or long-term version control.

Bluebeam project vs session: the core differences

  1. Purpose, Project = store, organize, and version documents. Session = collaborate on markups in real time.
  2. Editing model, Project locks one editor at a time (check-out). Session lets many people mark up at once.
  3. Lifespan, Project is long-lived (the whole job). Session is short-lived (a review cycle).
  4. What's tracked, Project tracks file versions. Session tracks individual markups and chat.
  5. Output, A Project holds the controlled master files. A Session produces a marked-up file you then file back into the Project.

When to use each

Use a Studio Project when…

  • You need a controlled home for the current drawing set and want clean version history.
  • Only one person edits a given file at a time, but the whole team needs reliable access to the latest revision.
  • You want the document set to persist and stay organized across months of work.

Use a Studio Session when…

  • You're running a coordination or QA review and several people need to redline together.
  • You want a time-stamped, attributed record of who flagged what.
  • The collaboration is time-boxed, open it, review, finish, done.

The two work best together

The common, sensible workflow on a live job: keep your masters in a Project, then when it's time for a review, push the relevant sheet(s) into a Session. The team marks up live; when you Finish the Session, the consolidated markups flow back into the Project as a new tracked version. Storage and control on one side, live collaboration on the other, each doing the thing it's actually good at.

A note from our studio

In our architecture practice in Vilnius, the real friction usually isn't choosing Project or Session, it's that the large CAD-export PDFs we push into these workflows (50-200 MB+ from AutoCAD, Revit and ArchiCAD) can feel heavy to pan, zoom and mark up, especially on a Mac. Studio handles the collaboration layer; the day-to-day editing performance on big drawings is a separate question worth solving on its own.

FAQ

Can I have a Project and a Session at the same time?

Yes. They're complementary. A typical setup is a long-running Project for storage and version control, with Sessions spun up as needed for live review cycles, then finished and filed back into the Project.

Do I lose my markups when I finish a Session?

No, finishing a Session consolidates the markups and lets you save or export the marked-up PDF. The key step is exporting or checking the file back into your Project before you finish, so the reviewed version is preserved in your controlled document set.

Does a Session keep version history like a Project?

Not in the same way. A Session records individual markups, chat and an activity log, but it doesn't give you the check-in / check-out file versioning that a Project does. For revision control over the document itself, the Project is the right home.

For heavy daily work on large 50-200 MB+ CAD drawings, the kind that bog down when you pan, zoom and redline them, a fast local desktop editor like Ncored runs entirely on your machine and stays smooth on big files; there's a free 14-day trial at ncored.com.