Get help with HTML to App

Contact the developer

Email support@htmltoapp.app with the step you were working on, what happened, and what you expected. Mention whether you were using a workspace project or Convert HTML to App.

What to include in a support request

• Whether you created a project, added an existing folder, or started from the Example Gallery.
• Whether your source is a single HTML file or a folder with index.html.
• Whether the content is fully self-contained or loads remote scripts, APIs, fonts, or media.
• Whether you exported with embedded content or from the original location.
• For launch issues, the exact macOS warning and whether the optional approval script is installed or needs an update.
• Relevant messages from Check Project or Checks & Output, with private project content removed.
• Which macOS version you are testing on and whether the issue appears in the source editor, preview, or exported app.

Expected behavior

• The current builder and exported launcher require macOS 12 or newer.
• Creating, editing, and exporting local projects works offline.
• Exports copy the precompiled launcher and use ad hoc signing for personal use and local testing. They are not distribution-ready.
• Save and Command-S write source edits to the original project folder. Use Duplicate Project for a separate copy.
• Previews and exported apps can access the network when the project's HTML loads remote resources.
• The workspace edits folders you approve. Sandboxed exports include read-only Downloads permission, plus source-folder access in reference mode and access to files or folders you authorize.

Help with the first launch

Read the first-launch and optional script guidance before changing anything. Local launch handling is separate from Developer ID signing, notarization, App Store approval, and macOS privacy permissions.