We're here
to help.

Any static website — HTML, CSS, JavaScript, images, fonts, and video. This includes single-page apps built with Vue, React, or vanilla JS, as well as multi-page sites and slideshow-style presentations. The app does not support server-side code (PHP, Python, Node.js) as it serves files directly without a backend runtime.

Anywhere accessible from the iPadOS Files app — iCloud Drive, On My iPad, a connected USB drive, or any third-party storage provider that integrates with Files (Dropbox, Google Drive, etc.). The app uses security-scoped bookmarks to remember your chosen folder between sessions.

No. ConcreteBlox Edge serves all files directly from local storage with zero network dependency. If your website makes outbound fetch() calls to external APIs, those require connectivity — but all local assets (HTML, CSS, JS, images, video) load entirely offline.

The most common cause is filename casing. iPadOS has a case-sensitive filesystem, unlike macOS. If your HTML references Logo.PNG but the file is saved as logo.png, the browser can't find it. ConcreteBlox Edge includes a case-insensitive resolver that handles most of these cases automatically, but it's best practice to ensure your HTML references match your actual filenames exactly.

This should not happen with ConcreteBlox Edge — the app fully supports HTTP Range requests (206 Partial Content), which is what video players need to seek. If seeking isn't working, ensure your video is in MP4/H.264 format, as this has the best compatibility with the iOS media player. WebM and OGV are also supported but may have limited hardware acceleration.

This usually means the app couldn't auto-select an entry HTML file. It looks for a file with "home" in the name first, then index.html. If neither exists, it shows a page picker. Try renaming your main HTML file to include "home" (e.g. home.html or demo-home.html), or use the sidebar picker to select the correct entry page manually.

Yes, fully. ES modules work because the app serves files over a custom URL scheme (localweb://) rather than the file:// protocol. Safari's security model blocks module imports on file:// — the custom scheme bypasses this restriction entirely. Vite, Webpack, and Rollup build outputs all work as-is.

Yes, as long as you have an internet connection. External resources like Google Fonts, cdnjs, or unpkg are fetched by WKWebView normally. If you need your site to work fully offline, download those resources and include them in your site folder — the app serves them at the same speed as any other local file.