Drag-n-Drop
to upload your archive
Upload your Angular build output and your app is live. No Firebase setup, no Google Cloud account, no CLI tools. Drag your ZIP file and get a shareable URL with SSL, analytics, and forms included.
Drag and drop files to upload.
Upload website file archives, images, documents, or PDFs.
Static.app supports the latest Angular output structure. Build with ng build, find your files in dist/your-project/browser/, ZIP them, and upload.
Add a 200.html fallback file for PathLocationStrategy. Or switch to HashLocationStrategy for zero-config routing. Either way, your Angular routes work on refresh.
Skip the Firebase CLI, the Google Cloud project, and the firebase.json configuration. Static.app deploys your Angular app with a single drag-and-drop.
Run ng build in your terminal. Angular compiles your app to dist/your-project-name/browser/ (Angular 17+) or dist/your-project-name/ (older versions).
Open the folder that contains index.html, main.js, and styles.css. Select all files and compress into a ZIP.
Drag the ZIP onto static.app. Your Angular app is live with a URL. Connect your domain and enable analytics from the dashboard.
HTTPS enabled automatically on every Angular app. No manual certificate setup.
Make quick changes to your deployed Angular app directly in the browser. Update text, fix paths, or adjust configuration files without rebuilding.
Share Angular app previews with clients behind a password. Toggle protection on and off from the dashboard.
How to host an Angular project?
Run ng build in your terminal. Angular compiles everything to the dist/your-project-name/browser/ folder (Angular 17+) or dist/your-project-name/ (older versions). Open that folder, select all files inside it, and compress them into a ZIP. Make sure index.html is at the root level of the ZIP. Drag the ZIP onto static.app and your Angular project is live with a URL you can share immediately.
Which Angular versions work?
All versions. The build output is always static HTML, CSS, and JavaScript. The output folder location differs between versions but the hosting process is the same.
Can I use Angular Universal (SSR)?
Server-side rendering with Angular Universal requires a running Node.js server, which Static.app doesn't provide. However, Angular Universal also supports prerendering, which generates static HTML at build time. Use prerendering to create HTML files for each route, then upload those to Static.app. The result looks and performs like SSR to the end user, but the HTML is served from the CDN instead of rendered per request.
Can I use Angular Universal for prerendering?
Yes. Prerendering generates static HTML for each route at build time without needing a running server. Configure your routes in the prerendering setup, run the build, and Angular outputs individual HTML files for each page. Upload these to Static.app and visitors get the same fast initial load as SSR, because the HTML is ready before JavaScript even executes. This is the recommended approach for Angular apps on static hosting.
How do I fix 404 on route refresh?
Create a 200.html file that's a copy of index.html. Place it in the root of your ZIP. Static.app serves it for any URL that doesn't match a physical file.
What about lazy-loaded modules?
Lazy-loaded modules work without any special configuration. When Angular builds your project, it creates separate JavaScript chunk files for each lazy-loaded module. Static.app serves these chunks on demand when the browser requests them. The initial page load downloads only the main bundle, and additional modules load in the background as the user navigates. This is purely a browser-side optimization that doesn't depend on the hosting platform.
Can I host Angular Elements (web components)?
Yes. Angular Elements compile to standard JavaScript files that register custom HTML elements. Include the compiled JS files alongside your HTML page and they work on any hosting platform. This is useful for embedding Angular components in non-Angular sites, creating widget libraries, or building micro-frontends. The compiled output is static files, making it a natural fit for Static.app.
Can I use multiple environments?
Yes. Angular's environment files (environment.ts, environment.prod.ts) are resolved at build time, not at runtime. Build with ng build --configuration production for production settings or create custom configurations in angular.json. Each build produces a separate set of static files with the correct environment values baked in. Upload the appropriate build output to Static.app for each environment (staging, production).
Do service workers work?
Yes. If your Angular app includes a service worker (via @angular/pwa), it works on Static.app. The service worker file is served like any other static file.
My assets aren't loading. Why?
The most common cause is the baseHref setting in your build. For root-level hosting on Static.app (your-site.static.domains/), the default "/" works. If assets still fail, rebuild with ng build --base-href ./ to use relative paths. Also verify that your assets folder is included in the ZIP. Check the browser console for 404 errors to see which specific files aren't loading and where the browser is looking for them.
Can GitHub host an Angular app?
Yes, GitHub Pages hosts Angular apps for free. You'll need to set --base-href to your repository name, configure a custom 404.html for routing, and either use a deploy script or GitHub Actions. Static.app is simpler: build, ZIP, upload. You also get built-in forms, analytics, a code editor, and password protection that GitHub Pages doesn't offer. Both options serve the same static build output.
SERVICE
FEATURES
UTILITIES
FORMATTERS
FRAMEWORK HOSTING
AI BUILDER HOSTING
ACCOUNT
One-click solution for your static website. Copyright © 2019-2026. All Rights Reserved.
By Designmodo