DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to export a dashboard as HTML, PDF, or PNG with DBT Charts

Render a board to a static file that you can send to people who do not run the CLI.

Who it is forAn analyst who must send a dashboard snapshot to a stakeholder or attach it to a report.

The problemStakeholders often need a fixed copy of a dashboard, not a live tool or a YAML file.

The outcomeA rendered file of the board in the chosen format, ready to share.

What you need first

  • Python 3.11 to 3.13
  • uv (or pip) to install the dbt-charts package
  • A warehouse adapter extra such as dbt-charts[snowflake] or dbt-charts[bigquery] if you want to run queries against your own warehouse
  • Warehouse credentials for your own data, or the Playground demo data at play.dbtcharts.com

Steps

  1. Run uv tool install dbt-charts to install the CLI.
  2. Run dct validate charts/guide.yml to confirm the board is valid.
  3. Run dct render charts/guide.yml --format html to write an HTML version. (inferred, check the README)
  4. Run dct render charts/guide.yml --format pdf or --format png if you need a different format. (inferred, check the README)

Prompt for your agent

In the dbt-charts repo, render the board at <placeholder> to PDF with `dct render <placeholder> --format pdf` and report the output file path. Verify that the file opens and shows the expected charts.

Caveat. Rendering needs real data from a warehouse or the demo data, so a board that queries an unreachable source will not produce useful output.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page