Tableau Versions Demystified
Tableau loves to make versions complex, so here's everything you need to know to keep Desktop, Server and Cloud working in lockstep.
- Tableau ships a new version roughly every quarter (e.g. one in March, then every three months) plus monthly patches that fix issues in already-released versions, including older ones like 21.3.
- The Tableau 'ESDALT' alternate download site is the best place to see every release and patch, with paid products (Desktop, Prep, Server, Online, Bridge) listed but not Tableau Public.
- Features are tied to versions: building with a new capability like the map intersects function and publishing to a Server that hasn't been upgraded means end users won't see it, and Server will warn you on publish.
- Since 2022, Tableau Server only gets feature updates twice a year (January and summer) rather than quarterly, though it still receives monthly patches and fixes.
- Tableau Cloud is managed by Tableau, requires no downloads or upgrades, and always works with the latest Desktop version, so you can update Desktop as often as you like.
Tableau ships new versions on a schedule, and if Desktop, Server and Cloud fall out of step, features you build might not work for people you share with. Understanding the release cadence stops you publishing something that quietly breaks for end users.
This applies to any organisation running Tableau Desktop against an on-premise or hosted Server, where the two can end up on different versions. It's less relevant to Tableau Public, which isn't part of this versioning system.
- Quarterly releases, monthly patches 0:29
Tableau puts out a new version roughly every quarter, and separately issues monthly patches that fix bugs in already-released versions, including older ones. A version being 'old' doesn't mean it stops getting patched.
- Use the ESDALT site to check versions 0:51
You can search 'Tableau ESDALT' to find Tableau's alternate download site, which lists every release and patch across the paid products (Desktop, Prep, Server, Online, Bridge). Use it as a reference to see exactly what version and patch level your organisation should be on — Tableau Public isn't listed there.
- Why lockstep matters 2:06
Know what version your organisation runs and keep Desktop and Server aligned to it. This isn't just tidiness — if you drift apart you risk building something that then fails to work once shared.
- Features are tied to specific versions 2:41
A new capability (the example given is the map intersects function) only exists from the version it was released in onward. If you build with it on a newer Desktop version than your Server has, that feature won't be visible to end users once published, and Server will warn you at publish time that it's not supported.
- Server's update cadence changed in 2022 3:28
Since 2022, Tableau Server only gets new features twice a year, roughly January and summer, rather than every quarter. This is a structural gap you need to account for when planning what features you can safely rely on Server supporting.
- Patches still matter even without new features 4:02
Even in the months Server isn't getting a feature update, it's still getting monthly patches and fixes, so it's worth keeping up with those updates rather than assuming there's nothing to install.
- Cloud removes the version problem entirely 4:33
Tableau Cloud is managed by Tableau directly, with no downloads or manual upgrades, and it always runs the latest version. If you're on Cloud rather than Server, you can update Desktop as often as you like without worrying about mismatch.
- The ESDALT site's name and purpose aren't officially explained by Tableau — it's just the practical way to see every release and patch in one place.
- Publishing a workbook that uses a feature Server doesn't yet support won't silently fail — Server flags it at publish time.
- An older Desktop or Server version can still receive a patch update well after its original release, so 'old version' doesn't mean 'no longer maintained'.
Check this before building anything with a newly released feature, or before planning an organisation-wide upgrade, so you know whether your Server will actually support what you design in Desktop.
How this Rollup was made provenance & method
A Rollup is drafted by AI from the video's transcript, then reviewed and edited by Tim. Everything used to produce this one is listed below — the model, the exact prompt, and the source video — so the process is transparent and reproducible.
- Transcription
- On-device — NVIDIA Parakeet v3 for recent videos, OpenAI Whisper large-v3 for earlier ones. The transcript never leaves the machine or gets published.
- Drafting
- Claude Sonnet 5 in the cloud, from that transcript.
- Prompt
- The exact Rollup prompt (v2) — the full system prompt, unedited.
- Source video
- Watch on YouTube
- Drafted
- 5 July 2026 at 09:38
- Reviewed & edited
- 5 July 2026 at 09:41 · by Tim Ngwena
Model + prompt + video is everything you'd need to recreate a Rollup like this yourself. The one thing we don't share is the transcript.
Rights. The video and its transcript are the property of TN Media Ltd. Unauthorised use or download is prohibited. © TN Media Ltd.