Preparing your game files

A game that ships its own files (instead of loading from a URL) is uploaded as its web build: the folder your engine or bundler exports for the browser, with index.html at the top. Deskifier puts that folder inside the desktop app and serves it from disk, so the game plays with no connection.

Upload the folder itself, or a .zip of it, up to 250 MB. It's fine if everything sits inside one folder in the zip; Deskifier unwraps it. Dotfiles and macOS __MACOSX folders are ignored.

Upload what your engine exports, not your project. If the folder has a package.json, a src/ folder or .ts files, it's probably your project; run your build and upload what it produces.

What to upload, by engine

EngineHow to exportWhat to upload
UnityBuild Settings (Build Profiles in Unity 6), platform Web / WebGL, then Build. First, in Player Settings > Publishing Settings, set Compression Format to Disabled, or keep compression and turn on Decompression Fallback.The folder Unity built: index.html with Build/ and TemplateData/ beside it.
GodotProject > Export > Add > Web, then Export Project into an empty folder. Name the export index.html.That folder: index.html with the .js, .wasm and .pck files Godot wrote.
ViteFor Phaser, Three.js, PixiJS, Babylon.js and the like: set base: './' in vite.config, then npm run build.dist/
Webpack, Parcel, CRAnpm run build. For Create React App, set "homepage": "." in package.json first.dist/ or build/
Plain HTML/JSNothing to build.The folder with index.html.
Construct 3Menu > Project > Export > Web (HTML5).The zip Construct downloads, as it is.
GDevelopFile > Export > Web, export to a local folder.That folder.
GameMakerThe HTML5 target, then Create Executable.The folder (or zip) it creates, with index.html at the top.
RPG Maker MZ/MVFile > Deployment > Web browsers.The deployed folder (it holds index.html, js/, img/, audio/).
DefoldProject > Bundle > HTML5 Application.The bundled folder.
Cocos CreatorBuild panel, platform Web Mobile or Web Desktop.build/web-mobile (or build/web-desktop).
PlayCanvasPublish > Download .zip (self-hosted build).That zip.
Ren'PyLauncher > Web > Build Web Application.The web build folder it creates.

If your game imports libraries or fonts from a CDN (three.js from jsDelivr, Google Fonts), that's fine: builds download a copy, so the game still starts offline.

Check before you upload

The dashboard checks your files as soon as you pick them, before anything is uploaded. With the CLI you can run the same checks on their own, without uploading or logging in:

npx @deskifier/cli upload ./dist --check

It prints what it found and exits with 1 when the files can't work as they are, so it fits at the end of a build script or an AI agent's loop: build, check, fix, check again. Add --json for machine-readable output (ok, errors, warnings, summary).

When the check passes, upload with deskifier upload ./dist (or deskifier create "My Game" --game --files ./dist for a new game).

What each upload error means

An error stops the upload, because the game would open to a blank screen. Each message names the file it's about.

  • "These look like a web page saved from a browser"
    The files came from a browser's Save page as (names ending in .download, a "saved from url" marker). A saved page is a copy of the website around a game, not the game. Fix: Export the game from your engine and upload that.
  • "Your index.html just opens https://…"
    index.html only frames or redirects to a game hosted somewhere else, so the game isn't in the files. Fix: Use that address as your game's URL instead of uploading files, or upload the game's own build.
  • "index.html loads src/main.ts…" or "Your game's code imports 'phaser' by package name"
    This is source code. Browsers can only run it through a dev server or bundler. Fix: Run your build (npm run build) and upload dist/ (or build/).
  • "index.html loads game.js, which isn't in your upload"
    A script or stylesheet the page needs is missing. Fix: Upload the whole build folder, not part of it.
  • "…asks for Game.js but the file is game.js"
    A reference and a file name differ only in capital letters. Windows and macOS ignore that; the desktop app doesn't, on any system. Fix: Rename the file or fix the reference so they match exactly.
  • "Your build expects to be served from /my-game/"
    The build was made for a website subfolder, so its file paths start with that folder. Fix: Set your bundler's base path to ./ (Vite: base: './'; Create React App: "homepage": ".") and rebuild.
  • "This Unity build is compressed in a way that needs special web server settings"
    Unity compressed the build (.br or .gz files) and expects the web server to unpack it. The desktop app can't. Fix: In Player Settings > Publishing Settings, set Compression Format to Disabled, or turn on Decompression Fallback, and rebuild.
  • "Your Unity build is missing Build/…"
    Files the Unity loader needs (.data, .wasm, .framework.js) aren't there. Fix: Upload the whole folder Unity built, including Build/.
  • "No index.html found at the root of your build" (the CLI: "…has no index.html at its top level" or "…at its root")
    The folder or zip doesn't have index.html where the build expects it. Fix: Pick the folder that directly contains index.html, not a folder around it.

A warning doesn't stop the upload. It's shown on the upload's card under Worth checking, and printed by the CLI:

  • A missing icon or image referenced by index.html: the game starts, but that file won't show.
  • A path in your game's code that only matches a file if capital letters are ignored, such as 'Assets/Player.png' for assets/player.png: that file may not load. RPG Maker and hand-written loaders hit this most.

The checks read your file names and your pages, scripts and stylesheets. They catch the mistakes above; a game that passes can still have bugs of its own, so try a dev build before you ship.