Export an app or template
Download reusable configuration as a portable .strive.html package.
A portable export packages an app so it can be inspected, previewed, and imported later. The file extension is .strive.html. Use export to transfer or reuse an app design, not to back up an app's live data.
Export
Open the app workspace and use its export/download action when portable apps are enabled. To export a template, select it in the New App template gallery and choose Download template. Keep the downloaded .strive.html file intact for later import.
What the file contains
The package describes the app definition, layout, components, events, data sources, theme, workflow recipes, prompts, declared record types, parameter schema, connection requirements, schedules, and supported private component definitions as applicable. It also records the runtime and catalog capabilities required to host it.
App table definitions can travel as empty schemas. Offline fixtures can demonstrate example content. App-specific documentation may explain how to configure and use the package.
What it does not contain
Live table rows are not exported. Credentials are not exported. Account-specific resources are represented as requirements or parameters rather than copied as proof of access. A package is not a clone of the originating tenant, live storage, completed workflow runs, reviews, retained documents, or private connection sessions.
During capture, sensitive values that can be safely parameterized become required inputs without stored defaults. Configuration that cannot be captured safely is refused. An export error about workflow references means you need to resolve the identified configuration; it is not an invitation to paste secrets into the package.
Preview and import
An offline-ready .strive.html file can carry a local renderer and fixtures. Offline preview does not reproduce hosted connections or start real workflows. A source envelope or plain export may not carry the offline renderer; the .strive.html extension identifies the package format, not a promise of identical offline behavior for every wrapper.
Import always reviews the destination's requirements. The receiving account must supply permitted connections, parameters, outputs, and compatible capabilities. To update only an existing app's interface, select the explicit update destination during import; backend and table-schema changes require a new app.
See Import an app, Save as template, and Custom components.