Just a download. Web tools are here.

Put your site in a .zip. The index.html closest to the top of the zip is the start page, and everything next to it belongs to the tool. Link your files with relative paths (css/style.css, not /css/style.css or a full web address).

• Up to 300 files and 50 MB in the zip, each file up to 4 MB. Bigger pictures, videos and sounds go next to the zip as media.
• File types the tool can use from the zip: HTML, CSS, JavaScript (also modules and web workers), JSON, CSV, text, pictures (PNG, JPG, WEBP, AVIF, GIF, SVG), fonts (WOFF, WOFF2, TTF, OTF), WebAssembly, sounds, videos and GLB models.
• Libraries like three.js go into the zip too: a web tool can't load anything from other websites (no CDNs, no Google Fonts).
• Then upload it under Upload → Web tool. Press Save any time: it's a project only you see, and Try it runs it exactly like visitors will. Our team checks it before it goes live.

my-tool.zip
├─ index.html        <- the start page
├─ css/style.css
├─ js/app.js
└─ img/logo.png

<!-- in index.html: relative paths -->
<link rel="stylesheet" href="css/style.css">
<script type="module" src="js/app.js"></script>

Keep your tool in a folder called tool and let a script build the zip. Our templates come with two, and the kit's file for your AI makes an AI set up the same:

• Preview.bat shows your tool in your browser (a double-clicked index.html can't load its own files).
• make-zip.bat builds dist/<name>.zip, the file you upload. It leaves out ff-dev.js, your ff-media copies and any ff-kit folder.
• Never put your own ff-kit folder in the zip: it replaces our kit on the site, and your tool loses the visitor's theme, the background and the icons.

my-tool/
├─ tool/          <- only this goes in the zip
│  ├─ index.html
│  └─ ff-dev.js    <- yours, left out
├─ Preview.bat
├─ make-zip.bat
└─ dist/my-tool.zip <- upload this

Not on our servers and not in the browser: a web tool runs sealed off, so it has no cookies, local storage or other browser storage, and it may not send anything anywhere. What people make stays on their own computer:

• Downloads work. Let people save their work as a file (for example JSON, PNG or a zip you build in JavaScript).
• Opening files works. A file picker (<input type="file">) or drag and drop lets them load it again next time.

Files in your zip people may download (a source file, an example): link them with download and use kit.js, or add ?download to the address: <a href="source/code.txt?download">. A plain link would open the file inside your tool.

// save: people download their work as a file
const file = new Blob([JSON.stringify(project)], { type: 'application/json' });
const link = document.createElement('a');
link.href = URL.createObjectURL(file);
link.download = 'my-map.json';
link.click();

// load it again next time: <input type="file" accept=".json">
picker.onchange = async () => {
  project = JSON.parse(await picker.files[0].text());
};

Media you upload next to the zip is used by name from the folder ff-media/, for example ff-media/Island-Map.png. The name is the file name with spaces turned into dashes; the upload form shows it for every file.

• Works anywhere a browser shows media: <img>, <video>, <audio>, new Audio() and CSS like background-image.
• Pictures, videos and sounds are shown, not read: a canvas or WebGL can't read their pixels. Need the pixels (for example a texture you edit, or a heightmap you sample)? Put that file in the zip instead.
• JSON, TXT and CSV files in ff-media/ (up to 4 MB) can be read with fetch().
• Use paths relative to the start page. From a page in a sub folder, write ../ff-media/.
• To swap a file later, press Replace on its card on your edit page (or upload one with the same name): the name in your code stays the same, no new zip needed.

<!-- shown: from ff-media/ (from a sub folder: ../ff-media/) -->
<img src="../ff-media/Island-Map.png">
<video src="ff-media/trailer.mp4" autoplay muted loop></video>

// read in code (canvas, WebGL, fetch): put it in the zip
const heights = await fetch('data/heightmap.json').then((r) => r.json());

Use ff-dev.js: a small file with a private link to your project. With it, ff-kit/ and your ff-media/ files load on your computer exactly like on FileFortress.

• Get it: Upload → Web tool → step 2 → Save & get ff-dev.js. Already saved? Your project → step 2 → ff-dev.js. Published already? Its edit page has it too.
• Put it next to your index.html and make it the first line in <head>.
• Keep it out of the zip, and don't share it (or paste it into an AI chat): it's your private link. New link replaces it.
• Looks plain and unstyled? The kit isn't loading: ff-dev.js is missing, not first, or you're looking at a preview inside another app instead of the file itself.

<head>
  <script src="ff-dev.js"></script>   <!-- first: only works on your computer -->
  <link rel="stylesheet" href="ff-kit/kit.css">
  <script src="ff-kit/kit.js"></script>
</head>

Yes, for the interface. The kit is served as ff-kit/ next to your tool, nothing to download. Build from its pieces (buttons, cards, tabs, fields, the top bar, the sidebar, sliders, dialogs, icons) instead of your own CSS:

• With kit.js your tool follows each visitor's site theme (FileFortress, Fortress Glow, Glass), and the site's background shows behind it. Colors you write yourself don't, and look wrong in the others.
• Your zip stays smaller and loads faster.
• Keep your own CSS for what no piece covers, and use the --ff- color variables there. Don't give html or body a background of your own.
• The kit never renames or removes a class, so what you build today keeps looking right.

Yes. Give the AI our file first: on the kit page, press For your AI. Without it, AIs reach for things that are blocked here (CDNs, browser storage, new tabs).

• The file makes the AI ask for ff-dev.js first, build the interface from the kit, set up Preview.bat and make-zip.bat, and use your tool's own name, not another website's.
• Read the code before publishing: you're responsible for what your tool does. Based it on someone's open-source code? Keep their license and credit them in the tool itself.
• Tick Made with AI when you upload (step 3, More details).

• 3D: yes, WebGL and WebAssembly work. Put the library and the models and textures it loads into the zip, so your code can read them.
• Sound and video: yes, play them with <audio>, <video> or new Audio(), from the zip or from ff-media/. Sounds you analyse or mix with the Web Audio API go into the zip.
• Games and viewers: pointer lock (for mouse look) and dialogs like alert() work.
• Python: only in the browser, built for WebAssembly and put in the zip. MicroPython (a few hundred KB) fits easily; Pyodide (numpy, pandas) is bigger than the 4 MB a file may be.

import * as THREE from './lib/three.module.js';  // in your zip, no CDN

const ground = new THREE.TextureLoader().load('textures/ground.png');
canvas.onclick = () => canvas.requestPointerLock();  // mouse look
new Audio('ff-media/theme.mp3').play();

To keep everyone who opens it safe, a web tool runs sealed off from the rest of FileFortress:

• It can't see who is signed in, and it has no cookies or browser storage.
• It can't connect to or load anything from other websites, and it can't send forms.
• It can't open pop-ups or new tabs, or use the camera, microphone or location. Fullscreen is our button: visitors press it, and kit.js tells your tool.
• It can't change the page around it: it lives inside its own frame on the asset page (and in the desktop app).

// these are blocked inside a web tool:
fetch('https://example.com/track');   // other websites
localStorage.setItem('save', data);   // browser storage
window.open('https://example.com');   // pop-ups and new tabs
document.cookie;                      // cookies and sign-ins

Three are ready, each on its own page with the download and the details:

• Docs: documentation for your asset. Write your pages in Markdown, it does the sidebar, search and the rest. Docs Template
• Interactive Map: a picture of your map with markers, categories and your own icons, made in the Map Maker (paste markers straight from UEFN), no coding. Interactive Map
• Web Tool Guide: the guide itself as a template, a full wiki with groups of pages and screenshots. Web Tool Guide

Every template comes with the FileFortress Template License: you may change it however you like, but the template's code and the tools you make with it may only be published and hosted on FileFortress. Everything you add yourself stays yours.