Creator guidelinesTool upload

Tool upload rules

How to prepare your files so the automatic check passes the first time.

Files and limits

  • Upload a ZIP, a single index.html, loose files or a folder. A file called index.html must be at the top.
  • Allowed: HTML, CSS, JavaScript, JSON, PNG, JPG, GIF, WebP, ICO, SVG, WOFF, WOFF2, TTF. No server files such as .php or .py.
  • Up to 5 MB for the ZIP, 2 MB per file, 200 files and 15 MB in total.
  • File names: letters, digits, “-”, “_” and “.” only, at most 3 folders deep, no hidden files.

How to build it

  • Everything inside the upload. No links to other websites for scripts, fonts or images, and no data sent anywhere. Tools run in a sealed box.
  • Scripts in files. Put code in app.js and load it with <script src="app.js">. No inline scripts and no onclick= attributes.
  • Relative paths. Use app.js, not /app.js.
  • No page title or description inside the tool. ToolsCrow already shows the name, the tagline and the description above the tool. Start with the controls.
  • Fluid width. Use <meta name="viewport">, percentages and max-width, never a fixed 1200 px layout.
  • Easy to tap. Buttons at least 44 px high and text at least 16 px on phones.

The example tool follows all of this and can be downloaded and edited.

Start from the example tool

This small bill splitter follows every rule on this page. Open it, try it at phone, tablet and desktop width with the buttons, then download the ZIP and change it into your own tool. It passes the automatic check as it is.

Fit

Questions people ask

Should my tool have a title (h1) inside?
No. ToolsCrow shows your name, summary and description above the tool. A second title inside the box wastes the space visitors came for, and two h1 headings confuse search engines. Start with the controls. Small headings for sections inside the tool (h2, h3) are fine.
Should it have a description or instructions?
Put the description in the details form. Inside the tool, only add short labels and hints right next to the controls.
What about a logo, header or footer?
Leave them out. The page around your tool already has the site’s header and footer.
How tall should it be?
Set a sensible height in the details form. If your tool changes height, the example shows the one-line message that lets the frame fit it exactly.
Can I save the visitor’s work?
Not in the browser: tools run in a sealed box without cookies or storage. Offer “Copy” or “Download” instead.

Every screen size

Before you can submit, the editor asks you to look at your tool on a phone, a tablet and a computer screen and to confirm that all three look right. Tools that only work on one size are refused.

The automatic check

Every file is scanned before anything is stored. If something is wrong, the page tells you exactly which file and rule, and how to fix it. Most refusals don’t count against your account; only attempts to hide harmful code do.

Review

After the check, a person looks at the tool and at how its name and description read. You get an e-mail when it goes live, when changes are needed, or when it is refused. See also the general guidelines.

Create a tool