HEVC/H.265 transfer

Send HEVC video with compatibility checked first.

HEVC is efficient, but support differs across platforms. FCShare inspects the file and asks the receiving browser only for the capability signals needed to make a useful recommendation.

Start the transfer

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

Choose a file.

Drop a file here or browse

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 B of 0 B —

—Speed

ConnectingPath

EncryptedIn transit

Delivered.

No copy was kept anywhere.

Stopped.

Ready

Room—

Route—

Payload—

The short answer

A successful transfer should not end with “it won’t play”

HEVC/H.265 may be excellent for storage and capture, yet unreliable in a particular browser/OS combination. Smart Send treats that as a preflight problem.

When H.264 appears as a recommended target, FCShare checks the sender browser itself. If HEVC decode and H.264/AAC encode are available, conversion runs locally in a worker and streams into the same WebRTC transfer. The untouched HEVC original is always sendable.

How to do it

Three steps, in the browser.

1
Choose the HEVC file
FCShare scans bounded MP4/MOV metadata locally.
2
Connect the recipient
Codec support is reported as supported, unsupported or unknown.
3
Choose the original or follow advice
No silent conversion occurs.

Best for

iPhone HEVC
Camera H.265 exports
Windows recipients
Mixed browser environments

What stays intact

HEVC original
No upload analysis
Minimal receiver profile
Technical reasons available on demand

Know before sending

Codec detection can be unknown in unusual containers
H.264 transcoding depends on sender-side codec support
Optimized streaming MP4 is fragmented
External playback apps differ from browser support

What gets inspected

FCShare looks for common ISO-BMFF codec/sample-entry markers and other bounded metadata. It does not parse arbitrary media indefinitely.

What “unsupported” means

It refers to the receiving browser capability probe, not every media player installed on the operating system.

Questions people ask

Will an HEVC file still transfer if the receiver cannot play it?

Yes, if the sender chooses Original.

Does FCShare install a codec?

No.

Can I see why it recommended H.264?

Yes, under Technical details.