When your source needs a build

Why source is rejectedCopy Anchor Link

A .ts, .tsx, .jsx, Vue/Svelte source file or Sass/Less stylesheet is not necessarily a browser-ready static asset. The same BUILD_REQUIRED guidance applies to direct uploads, source files inside ZIPs, API file payloads and recognizable framework source pasted into the HTML field.

DeployHTML hosts the finished website. It does not install dependencies, run your build command or start an application server for each project.

Build with your project's instructionsCopy Anchor Link

Use the build/export command documented by your framework or coding tool. For an existing npm project this may be npm run build, but the correct command and output directory are project-specific.

Inspect the resulting directory. It should contain index.html and the files the browser will request. Upload the contents of that static output, rather than package.json, source files and node_modules.

Finished output to upload:
  index.html
  assets/app.js
  assets/style.css

Source repository to build first:
  package.json
  src/App.tsx
  node_modules/

For a small AI-generated pageCopy Anchor Link

Ask for one complete self-contained HTML document with its CSS and browser JavaScript included. Review it locally, then paste or upload the HTML.

If the build needs a serverCopy Anchor Link

A server-rendered backend, private connector or database cannot be moved to static hosting by ZIP compression. Use a supported static export, or host the server separately and verify its integration. Keep secrets on that server, not in the browser.

Use the ZIP checklist after you have the finished static files.