Home / Reel Share Link Transcript
Can You Paste an Instagram Reel Share Link for a Transcript?
Yes, a complete public Reel URL can be pasted into XAPN even when it includes a share-style query parameter after the Reel path. In our live check, the example Reel with ?igsh=example passed URL validation, returned audio, and produced visible text in the browser. This does not mean every shared link or every Reel will work: it must still point to a reachable individual Reel with speech.
The link we actually checked
On October 11, 2026 (Los Angeles time), we used the public example Reel already shown in XAPN's input. We appended the synthetic share-style suffix ?igsh=example to its /reels/ URL. This suffix was a test value, not a claim that Instagram issued that exact share token. We sent both the clean URL and the parameterized version to the live GET /api/agent URL-pattern check. Both returned valid_public_reel_url: true. That route only checks the shape; it does not fetch media.
Next, we posted the parameterized URL to XAPN's live /audio route. It returned HTTP 200, audio/mp4, and 317,657 response bytes. Separately, in the Codex in-app browser, we replaced the homepage input with that same parameterized URL and selected Get transcript. The page first showed the audio-fetch status and later Done. with 1,149 characters in the result area. We did not republish the creator's words or compare this run word-for-word with the clean-URL run.
The site code explains the boundary. Its server accepts Instagram /reel/ or /reels/ paths and passes the submitted URL to audio retrieval. The browser recognizes speech only after the audio response arrives. A URL-pattern success therefore does not prove the Reel is public, still available, or intelligible. An Instagram profile link is a different input and was rejected in our account-link check.
Test boundary: one public example, one synthetic query suffix, one browser run. We did not test all Instagram share parameters, short-link redirects, private Reels, or different creators' posts. The result supports trying a complete share URL first, not a blanket compatibility guarantee.
From copied link to usable text
- Copy the URL of the individual public Reel, not the account profile. Keep its complete link when you first paste it.
- Use the transcript tool and wait for Done. plus actual words. A validated URL by itself is not a transcript.
- Review the words against the Reel audio. Then use Copy or Download .txt to keep the result.
If fetching stops, check the link's availability and the exact status in the failure-stage guide. If the path uses /reel/ rather than /reels/, the two-path test addresses that separate URL question. Neither path nor a query suffix can turn a private or silent Reel into a usable spoken transcript.
Questions
Should I delete everything after the question mark? Not as a required first step. The tested parameterized link worked. If your particular link fails, diagnose its failed stage rather than assuming the query is the cause.
Does valid_public_reel_url: true prove the Reel is public? No. It reports a matching URL pattern only; audio retrieval and speech recognition are separate steps.
A share-link suffix should still point to one public Reel. Paste that URL to convert a Reel to text through the same audio path. If retrieval fails, test the clean Reel URL before blaming the transcript step.