What Glide does and does not export
Glide is a builder for data-backed apps built on spreadsheets, and the app shell is proprietary and never leaves Glide. Even where an export exists, it hands you raw files rather than the specific structure WordPress expects — a theme header, a stylesheet WordPress recognises, and templates that render.
Anatomy of a valid WordPress theme
WordPress will only accept a .zip containing a theme folder with a metadata header, an entry template, and correctly referenced assets. That structure is what a hand port spends most of its time producing.
- A theme folder with a recognisable name
- A stylesheet carrying the theme header
- An entry template that renders the page
- Relative asset paths that survive the upload
Producing the .zip from a rendered page
Themify writes that structure for you. It reads the fully painted page at a *.glide.page app URL, rewrites every asset reference to a local path, and packages the result.
- Open the page you want to convert in Chrome.
- Click the Themify extension icon in the toolbar.
- Press Generate theme and wait for the capture to finish.
- In wp-admin, go to Appearance → Themes → Add New → Upload Theme.
- Upload the .zip, activate it, and the page is live on WordPress.
Checking the export before you ship
Install the theme on a staging site first. Confirm fonts load, images resolve, and interactive elements still respond. Because the capture includes the app shell layout and its component styling, most issues come from assets that were behind a login rather than from the conversion itself.
Frequently asked questions
- Does Glide have a WordPress export?
- Not one that produces an installable theme. Themify fills that gap by packaging the rendered page as a valid theme .zip.
- Where do I upload the .zip?
- In wp-admin: Appearance → Themes → Add New → Upload Theme, then activate.
- Is the theme self-contained?
- Yes. Every stylesheet, script, font and image referenced by the page is bundled inside the .zip.