A dashboard's arrangement can be worth keeping even when its data and business question change. Rebuilding nested containers, spacing and text from scratch adds work before you have begun the new analysis.
Datacooper's Tableau Layout Extractor is designed for that narrower task: take a workbook and produce a reusable structural starting point. The image above is a real screenshot of the current tool page, captured on October 11, 2026. It shows the input, output and limits; it is not a screenshot of a completed extraction or a validated Tableau rendering.
What goes in and what comes out
The current form accepts a TWB or TWBX workbook. You can optionally specify dashboard names and choose filenames for the layout JSON and layout-only TWB output.
The intended output contains containers, blank objects and text objects. Charts, data sources and worksheet content are outside that layout-only output. This distinction is useful when you want to keep the arrangement while replacing the analysis.
For example, suppose a team likes the hierarchy of an existing executive dashboard: a title, a KPI row and two detail panels. A layout skeleton gives the next project a place to start. The new project still needs its own data connections, worksheet definitions, calculations and interactions.
Keep structure separate from meaning
A layout JSON file makes the arrangement inspectable. A layout-only workbook gives a Tableau developer an artifact to review and extend. Neither establishes that the new dashboard answers the right question.
Before treating the output as a reusable template, review it in Tableau Desktop:
- Check container nesting, dimensions, spacing and retained text.
- Replace text that belongs to the old business context.
- Bind new worksheets to the appropriate data and metric definitions.
- Check filters, actions and relevant dashboard states after adding the analysis.
These are recommended checks, not a claim that I ran a new extraction or completed those checks for this article. Today's verification covers the live tool page and its form implementation. The frontend sends the tableau_file_to_layout action with objects_only restoration mode to the existing server-side executor.
What the historical post does not establish today
My original post described this layout-reuse direction and mentioned tiled layouts. I am not extending that historical note into a current floating-layout compatibility promise. Review the particular workbook you intend to reuse.
I am also not repeating the old blanket claim that no uploaded data is stored. The current page identifies a server-side executor. Submit only files you are authorized to process and establish suitable handling requirements before using sensitive workbooks.
The open-source cwtwb repository is the broader workbook engineering context. Datacooper's planned paid MCP is a separate product direction: help carry a BI task through clearer inputs, construction and review. Access is not open yet; this article does not announce a paid service launch.
Try the focused Tableau Layout Extractor, and review its output before incorporating it into a new dashboard.
Sources and project links
- Original historical post — retained as a source only.
- Current tool description, inputs and limits.
- cwtwb on GitHub.
- Public workbook replication cases.
- Datacooper and planned MCP early access.
Top comments (0)