Exporting Widgets
You can export a widget as a self-contained HTML file that runs independently in any browser, without needing access to Crow's Nest.
How to export
- Open the widget in the widget editor.
- Click the Copy button in the toolbar.
- The exported HTML is copied to your clipboard (or downloaded as a file, depending on the widget).
The exported file contains everything the widget needs: your HTML, JavaScript, CSS, data connection credentials, and a bundled runtime library.
What's included in the export
- Your widget code (HTML, JS, Chart.js, CSS)
- A runtime library that provides
getData(),getTheme(), and other SDK functions - Embedded configuration for each data connection (Tulip credentials, SQL config references, static data rows)
- Widget SDK script for the standard API surface
Export modes
There are two runtime bundles:
- Full runtime — Includes the Tulip API client library. Exported widgets can fetch data from Tulip directly.
- Lite runtime — Smaller bundle that relies on an external proxy for data fetching. Used when a proxy URL is configured.
The export system selects the appropriate runtime automatically based on your configuration.
Limitations
- SQL connections — Widgets that use SQL connections cannot be exported via the copy button, because SQL queries must run server-side. The copy button is disabled for these widgets.
- MQTT connections — Real-time MQTT subscriptions work in exported widgets if the broker is accessible from the browser.
- Credentials — Exported HTML files contain embedded Tulip auth tokens. Share them carefully and only with authorized users.
Max dimensions
The Max Width and Max Height settings in the widget editor's Settings tab control the maximum size of the exported widget. These are set in grid units and are primarily used for dashboard layout, but also affect how the export renders.
Use cases
- Embed a widget in another application or intranet page
- Share a visualization with someone who doesn't have a Crow's Nest account
- Archive a widget as a standalone file