Publish your converted workbook ¶
Check the preview first ¶
After conversion, use Open preview and review the Messages tab. Test the inputs, calculations, charts and controls before sharing the result.
Choose a destination ¶
The conversion result offers publishing choices. The primary publishing button remembers the destination you selected; use the other options when you want to change it.
- Download zip: download the project files for hosting yourself. Keep the bundle together rather than copying only the first HTML file.
- Test in cloud: create a temporary test link.
- Publish to cloud: use the permanent cloud link.
- Publish to Server: publish to SpreadsheetConverter Server when a Server destination is configured.
- WordPress instructions: open the instructions for that publishing destination.
Node.js projects are for self-hosting; use Download zip. The classic Test in cloud and Publish to cloud destinations are unavailable for Node.js output.
For the differences, practical uses and returning to unfinished forms, compare Publish to cloud and Publish to Server.
Publish to SpreadsheetConverter Server ¶
Server publishing uses an authenticated session. If automatic sign-in fails, sign in with Microsoft in the task pane and try publishing again. The add-in reports a rejected workbook separately from a Server service problem; read the reported reason before changing your spreadsheet.
A successful publish provides the form link and any warnings. A warning does not by itself mean that publishing failed. If the Server refuses the workbook and offers See what to do, open that explanation.
Embed a published form ¶
Where the publishing result offers Copy embed code, copy that code into the destination page. The current embed code is one script line; use the supplied code rather than constructing the runtime address yourself.
Your website editor must allow the script. WordPress and other editors can remove code that the current account is not allowed to insert. Check the saved page and test the actual embedded form after publishing it.
Share a calculator by email ¶
Publish the calculator and email its link rather than expecting a JavaScript calculator to run inside an email message. Sending submitted form data by email is a separate workflow: configure the submission destination and test delivery.
Keep calculation logic confidential ¶
HTML calculations run as JavaScript in the end user’s browser. Do not use browser-calculated HTML output to keep calculation logic confidential. If you need to protect that logic, select a supported server-side calculation mode and verify that the resulting browser assets do not contain it.
Check hosting capacity ¶
For browser-calculated HTML, the generated files can be served as static web assets. Server-backed calculations and submission endpoints have their own capacity requirements. Test the actual generated bundle and hosting configuration rather than relying on historical page-size estimates.
Automated conversion ¶
Version 12 includes a command-line conversion tool and an authenticated conversion service. These workflows require the normal account and licence checks; supplying an email address manually does not establish entitlement.