What a drop is

The basics

• A drop is a single web page: an HTML file, a React or Vue component, a static bundle from a ZIP file, or a PDF. See Building and importing for what can be uploaded.
• A drop has no server of its own. All of its code runs in the visitor's browser. Saving data, calling an AI model and collecting feedback go through services that Toolcrow adds to the page.
• The maker manages each drop on its drop page in the Toolcrow app. The top of the page shows the name, the version ("v3 · updated 2 days ago"), the buttons "Change with your AI" and "Open drop", and two round buttons: Live (turn off, turn on, delete) and how it is shared (Private, Password or Open). Below that, "Needs you" lists what is waiting for the maker (a broken connection, an update from their AI, new reports), followed by the tiles Sharing, Usage and Connections, with a small Submissions tile under Connections about the Toolcrow database: "Saving", "Only what failed" (when the copy is turned off), "Not in use" (a chosen Google Sheet takes its place) or "Not saving" (the tool keeps nothing). Its arrow opens the Submissions page. The arrow on a tile opens its details: Sharing opens a window to change who can open it, send the link and set what visitors can do; Usage and Connections open a side panel (visits over 7 or 30 days, where submissions are saved, AI use per day and reports; and what the tool talks to, split into what Toolcrow runs and what the tool calls itself). In the Connections panel, "Manage" or "Review" opens the panel of one connection, the same one as on the Connections page, with what this drop does with it on top; "Add a connector" (under "Through Toolcrow") connects a service to this drop step by step, and the panel shows where submissions go, with the switch "Keep a copy in Toolcrow" when the drop forwards to a webhook; "How it's built" shows what Toolcrow saw in the code. The submissions themselves are on their own Submissions page (the arrow on the Submissions tile, or "View" in a panel). The drop page has no tabs: everything is on this one overview.
• Drops do not expire. A drop stays online until the maker turns it off or deletes it.

Where a drop lives

• Every drop is served from its own address on toolcrow.live, a random subdomain such as https://<label>.toolcrow.live. This is a separate domain from the Toolcrow app (toolcrow.app).
• Because each drop has its own address, the browser keeps each drop's storage separate: one drop cannot read another drop's data or the visitor's Toolcrow session.
• Older share links of the form www.toolcrow.app/<name>/<slug> forward to the drop's own address.
• Drops are kept out of search engines (noindex on every response). A drop is found through its link, not through Google.

What Toolcrow adds to every drop

Toolcrow injects a small runtime script into every drop page. The maker's own HTML and code run unchanged; the runtime adds:

• Storage: localStorage and sessionStorage keep working and survive refreshes (see Saving data).
• Shared data: Tooldrop.opslaan() / Tooldrop.lezen() for submissions and window.storage for shared values (see Saving data).
• AI: window.claude.complete() and AI calls without an API key (see AI inside a drop).
• The "Powered by Toolcrow" badge: shown on every drop. On open drops it also opens a share panel with a "Report abuse" link.
• A feedback button, when the maker turns feedback on for that drop (see Feedback and Nest).

A copy of a free tool

Toolcrow's own free tools on toolcrow.app/tools have a "Make this your own" button. A signed-in maker who clicks it gets a copy of that tool as a new drop in their own account, and lands on its drop page. Without an account, the button asks to sign in or sign up first (signing up needs an invitation code during the beta).

• The copy is private, like every new drop: only the maker can open it until they change who has access in the Sharing window.
• Only the tool's code is copied. The copy starts without the original's password, connections, feedback, saved data or settings, and is scanned like any new drop.
• The copy belongs to the maker and stands on its own: they can change it like any other drop, for example with their connected AI (see Connecting your own AI), and later changes to the original never reach the copy.
• A maker can make 10 copies per day. A second click within a couple of minutes opens the copy that was just made instead of making another one.

Language of the frame

The badge, the share panel, the feedback button and Toolcrow's own screens around a drop (password, private, turned off, not available) are in English or Dutch. They follow the tool's own language, set in its first HTML tag: <html lang="nl"> gives a Dutch frame, <html lang="en"> an English one. Without that, the frame follows the language of the visitor's browser, and otherwise it is English. On the password, private, turned-off and not-available screens the visitor can switch with "NL | EN"; that choice wins and is remembered in their browser for that drop. A pasted React, Vue or JavaScript snippet has no <html> tag of its own, so its frame follows the browser. Toward visitors the frame says "tool", not "drop".

Status of a drop

• Live: visitors who have access see the tool.
• Turned off: the maker switched it off with the Live button on the drop page. Visitors see an "inactive" page with a button to ask the owner to turn it back on. Turning it on again restores it as it was.
• Deleted: the link no longer works. To delete, the maker types the drop's name to confirm.
• Taken down by Toolcrow: after an abuse report, Toolcrow can block a drop. Visitors see "This tool is not available". The maker sees the reason on the drop page and cannot turn it back on themselves.