Home / MP4 Upload Fallback

Can You Upload a Reel MP4 When the Link Fails?

No, not on XAPN today. This tool takes one public Instagram Reel URL; it has no MP4 file picker or upload route. If the link fails, note the exact stage first. If you own an authorized local copy, use a separate transcription tool that explicitly accepts MP4 uploads, or transcribe the audio manually. Do not mistake XAPN's internal audio retrieval for a file-upload feature.

Try a public Reel link
A public Reel URL can enter XAPN's audio workflow, but a local MP4 file has no upload input or endpoint on this site.
The link route and a local-file upload are separate capabilities.

What we checked

On October 14, 2026 (Los Angeles time), we fetched XAPN's live homepage. It returned HTTP 200 and displayed an Instagram Reel URL field, Get transcript, Copy, and Download .txt. We checked the served markup for a file input and multipart upload form; neither was present. The page sends the URL string to /audio and recognizes the returned audio in the browser. The .txt control saves recognized words after a run; it does not load a source video.

We then fetched the site's public /openapi.json, which also returned HTTP 200. It did not declare an /upload path or a multipart file request. A direct empty JSON POST /upload check returned HTTP 404. That test did not send a video or any personal file. It checks a route's availability, not whether a particular MP4 could be decoded by another service.

The local server implementation agrees with the live response: its audio route reads one JSON url value, retrieves media for an accepted Reel address, and returns audio bytes. It does not read an uploaded file body for transcription. The server's preferred media choice is audio, with a fallback, so this inspection does not guarantee that no video bytes ever transit the service. What it does establish is that visitors are not asked to choose and upload a local MP4 in this workflow.

Evidence boundary: live page and OpenAPI inspection, one empty upload-route request, and server-path review. We did not upload or transcribe an MP4. We did not test Instagram permissions, private media, or another vendor's file-upload feature.

When a link-based run stops

  1. Check whether you copied an individual public /reel/ or /reels/ link. A profile or ordinary /p/ post URL is a different input type.
  2. Read the status shown by the tool. If it stops during fetching, inspect the link and Reel availability; if it stops after audio arrives, use the failure-stage guide for the model and decoding stages.
  3. If you legitimately possess an MP4 and need an upload fallback, use a tool that clearly documents MP4 import, privacy handling, language support, and export format. XAPN cannot receive that file.

For a working public link, the simpler route remains paste, run, review, and save the text. You do not need to download and re-upload a video first. If your actual requirement is many Reels at once, see the separate batch-workflow boundary; a local MP4 upload would not make this single-item interface a batch tool.

Questions

Can I drag an MP4 onto the page? The checked page has no file-drop or file-picker control. Use a service that explicitly offers file import.

Does Download .txt let me upload the video later? No. It saves the current recognized text, not the source video or audio.

An MP4 upload is not available on this link-based path. With a reachable public URL, you can convert a Reel to text without handling the video file. Use another service when the only source you have is a local upload.