Share Sheet Prefill Tester

Test what social apps actually do with Web Share API payloads.

Test Scenarios
1
Text Only
Just a caption string. No URL, no files.
title: "Brand Challenge" text: "I'm joining the Brand Challenge — want in? #BrandChallenge"
2
Text + URL
Caption with a campaign link. Many apps append the URL to the text.
title: "Brand Challenge" text: "I'm joining the Brand Challenge — want in? #BrandChallenge" url: "https://mobile-sharesheet-prefill.pages.dev?utm_source=share"
3
Text + URL + Image File
Full payload with a branded share card as a file attachment.
title: "Brand Challenge" text: "I'm joining the Brand Challenge — want in? #BrandChallenge" url: "https://mobile-sharesheet-prefill.pages.dev?utm_source=share" files: [brand-share-card.png]
4
Image File Only
Just the branded image, no text or URL. Tests whether some apps show the image but ignore everything else.
files: [brand-share-card.png]
5
Caption Baked into URL
No text field — the campaign message lives in the URL's hash fragment. Tests if any apps display or use it.
url: "https://mobile-sharesheet-prefill.pages.dev?utm_source=share#caption=I'm+joining+the+Brand+Challenge"
6
Long Text + Multiple Hashtags
Tests truncation behavior — some apps cap the prefilled text length.
text: "I just completed the Brand Challenge and it was amazing! Check out my results and join in on the fun. Who else is up for the challenge? Let's see what you've got! #BrandChallenge #Viral #Challenge #JoinMe #Trending" url: "https://mobile-sharesheet-prefill.pages.dev?utm_source=share"
Custom Payload
C
Build Your Own
Fallback: Copy to Clipboard
If Web Share isn't available, this copies the caption + URL so users can paste into any app.

Event Log

--:--:-- Waiting for shares...