Appearance

Updating visuals

If you see any images containing outdated UI, please bear with us.

We are updating all content as quickly as possible to mirror our new UI.

Files ​

Use Files in the Assets panel to upload static files to WeWeb's CDN. You can then link to those files, or set a path so they are available at a specific URL on your published app.

This is useful for files that need a known public URL, such as a custom sitemap, robots.txt, a PWA manifest, a service worker, or a verification file for a third-party provider.

Open project files ​

  1. In the top bar, open the Interface tab.
  2. In the left panel, open the Assets tab.
  3. Click Files.

This opens the Project files popup.

Project files

Upload a file ​

  1. Open Project files.
  2. Click Upload new file.
  3. Choose one or more files from your computer.

Uploaded files are stored on WeWeb's CDN. From the file row, you can:

  • Copy link To get the CDN URL
  • Download file To download the original file
  • Delete To remove the file from the project

FILE SIZE

Uploaded files cannot exceed 50MB. If a file is too large, WeWeb shows an error and skips the upload.

Set a path ​

Set path controls where the file is available on your published app.

  1. Open Project files.
  2. Find the file, then click Set path.
  3. Enter the path where the file should be available after publish, for example /sitemap.xml.
  4. Click Save.
  5. Publish your app so the path goes live.

After publish, the file is available at that path on your domain. For example, if your app is on mydomain.com and you set the path to /sitemap.xml, the file is available at mydomain.com/sitemap.xml.

Setting a path overrides the file WeWeb generates by default at that location.

Path rules:

  • Use letters, numbers, /, ., -, and _ only
  • Do not end the path with /
  • Leave the path blank and republish to remove the file from that deploy path

TIP

Clearing the path removes the file from the published app path after you republish. The file stays on the CDN until you delete it.

Common examples ​

Common examples include but are not limited to:

  • A custom sitemap (/sitemap.xml), robots.txt, PWA manifest (/manifest.json), or service worker (/serviceworker.js)
  • Verification files for third-party providers such as Apple Pay
  • Static files (for example PDFs and CSVs) to display in or download from the app

Custom sitemap ​

Upload an .xml file and set its path to /sitemap.xml. After publish, it overrides WeWeb's auto-generated sitemap.

Learn more about custom sitemaps →

LLMs.txt ​

Upload a text file and set its path to /llms.txt.

Learn more about LLMs.txt →

Custom PWA manifest or service worker ​

If you need to replace WeWeb's default PWA files:

  1. Upload your custom file.
  2. Set the path to:
    • /manifest.json For a custom PWA manifest
    • /serviceworker.js For a custom service worker
  3. Make sure PWA is enabled for your app.
  4. Publish your app.

CUSTOM SERVICE WORKER

A custom service worker requires the PWA to be enabled in app settings. Otherwise, the published app unregisters all service workers.

To enable PWA:

  1. Open the Settings tab in the top bar, then open Interface Settings.
  2. Open Mobile app (PWA).
  3. Set Enable Mobile App (PWA) to Enable.
  4. Save, then publish.

Learn more about Mobile app (PWA) →

Project files vs user files ​

Assets → Files is for app files you want available on your published project.

For user-uploaded content (profile photos, documents tied to accounts, and similar), store files in a backend or storage system with access controls. That approach scales better and keeps user data secured per user.

TIP

If you use WeWeb Backend, look at Storage in Data & API for user file workflows. Project files in Assets are a different system.