Lovable/prompt
Build with a prompt
Opens Lovable with a prompt, and optionally image or page references, then starts building.
Format
https://lovable.dev/?autosubmit=true#prompt={prompt}&images={images}&html={html}Try it
https://lovable.dev/?autosubmit=true#prompt=Rebuild%20this%20page%20with%20our%20logo&html=https%3A%2F%2Fexample.com%2F&images=https%3A%2F%2Fimg.example.com%2Flogo.pngOpen
What you supply
{prompt}What to build. Maximum 50,000 characters.
URL-encode it. It sits in the fragment, so an unencoded
#truncates it — and a+here is a literal plus, not a space, because fragment parsing is Lovable's, not a form decoder's.{images}optionalA publicly reachable image URL used as a visual reference (JPEG, PNG, or WebP).
URL-encode the whole image URL. Repeat the key for several images (
images=…&images=…). SVG and GIF are ignored; the rest of the link still builds. The Link Generator can upload images so they do not need to stay publicly hosted.{html}optionalA publicly reachable web page URL whose layout, content, and styling Lovable may use as a reference.
URL-encode the page URL. Repeat the key for several pages. The page must be a normal HTML document over public
httporhttps— private, authenticated, andlocalhostURLs are skipped silently.
The prompt travels in the fragment, not the query string. #prompt=… rather than ?prompt=…,
which is unlike every other entry in this registry and has two consequences worth knowing.
The first is a feature. A fragment is never sent to the server: it does not appear in Lovable's
access logs, it is not in the Referer header when Lovable's own page later loads a third-party
asset, and a proxy between you and them cannot read it. Of all the ways to hand a prompt to a hosted
tool, this one leaks the least.
The second is a trap. Anything that rewrites URLs is entitled to drop a fragment — link shorteners, tracking wrappers, some chat clients' unfurlers, an HTTP redirect that does not preserve it. The link will still open Lovable, still look like it worked, and the prompt will simply be gone. If a Lovable link arrives empty, suspect whatever forwarded it rather than the link.
autosubmit=true does what it says: the build starts on load, without waiting for the person to
read what they are about to run. Drop the query parameter to have it fill the box and stop. A
signed-out clicker is sent through sign-up first; after they authenticate, the original prompt and
references are preserved and the build continues.
Reference attachments
images and html are optional, and they share a combined limit of 10 attachments per link.
Both are fetched by Lovable's servers, so each URL must be publicly reachable over http or
https. Non-public, malformed, or (for images) non-raster URLs are dropped silently — the app
still builds from the prompt and whatever attachments survived.
Repeat a key to pass more than one:
#prompt=…&images=URL1&images=URL2&html=PAGE1
The official Build with URL docs and the Link Generator are the sources of truth when the encoding gets long.