iPhone video → Windows

Send an iPhone video to Windows — and know if it will play.

Choose the iPhone video first. When the Windows browser connects, Smart Send checks compatibility locally and keeps the original available at every step.

Start the transfer

Either way you get a code. Whichever device has a camera scans it.

Choose a file.

Scan this.

Or open the link, or type the name.

—

Enter the code.

Smart Send

Recipient ready.

Checking whether the original file is the best fit.

Recipient capabilities are approximate and temporary.
Original

Original file

Best quality

Technical details

FCShare never changes your original file. Optimization only happens after you choose it.

Save this?

    Transferring

    Moving now.

    0%
    0 B of 0 B —
    —Speed
    ConnectingPath
    EncryptedIn transit

    Delivered.

    No copy was kept anywhere.

    Stopped.

    Ready
    Room—
    Route—
    Payload—
    The short answer

    The transfer can understand the Windows side

    Recent iPhones commonly record video in formats that are efficient on Apple devices but not equally reliable on every Windows browser. FCShare inspects the selected file on the sender and receives only a coarse capability summary from the recipient.

    If the original looks compatible, it stays on the normal direct-transfer path. If HEVC, 4K resolution, storage or another practical issue is detected, the sender sees a recommendation and can still choose the untouched original.

    How to do it

    Three steps, in the browser.

    1. 1

      Choose the iPhone video

      The file stays on the sender while FCShare inspects container, codec and size locally.

    2. 2

      Connect the Windows device

      Share the room link or QR code. The Windows browser reports only the compatibility signals needed for this transfer.

    3. 3

      Choose what to send

      Send the original, or use a locally available optimized copy when the browser can safely create one.

    Best for

    • iPhone HEVC/H.265 recordings
    • Large 4K phone videos
    • One-time Windows handoff
    • Original-quality transfer when compatibility is already good

    What stays intact

    • Original always remains available
    • No server-side transcoding
    • No account
    • Encrypted WebRTC transfer

    Know before sending

    • Local conversion depends on sender browser codec support
    • On-the-fly MP4 output is fragmented for bounded-memory streaming
    • Optimized media keeps primary video/audio tracks; use Original for alternate tracks/subtitles
    • Both devices stay online

    Why HEVC matters

    A MOV file can transfer perfectly and still fail to play if the receiving Windows/browser stack cannot decode its video codec. Smart Send separates transfer success from playback compatibility.

    What FCShare changes

    Nothing is changed silently. When the sender browser can safely decode and encode the required codecs, FCShare can remux or transcode locally while the output is already moving through WebRTC. The VPS never performs the conversion.

    Questions people ask

    Will FCShare convert my iPhone video automatically?

    No. It never silently modifies the file. The sender explicitly chooses an optimized version, and the option is enabled only after the sender browser proves the local conversion path is available.

    Does the video upload to FileCarpenter for analysis?

    No. File inspection happens on the sender device.

    What if Windows can already play the original?

    FCShare keeps the normal original transfer path instead of adding unnecessary processing.