Large video transfer

Send a large video with the receiving device in mind.

FCShare keeps the original-byte transfer path, then adds compatibility, storage and time estimates when they can prevent a failed handoff.

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

Large transfers fail for more than one reason

A video can be too large for a messaging service, too large for available browser staging, or perfectly transferred but unplayable because of its codec. Smart Send considers those separately.

The file still moves through the existing WebRTC DataChannel with the same backpressure and receiver-side save logic. Adaptive advice sits above that path rather than replacing it.

How to do it

Three steps, in the browser.

1
Choose the video
FCShare inspects only bounded local metadata.
2
Connect the recipient
Capability and storage signals are deliberately coarse.
3
Send original or follow a recommendation
Actual transfer reuses the proven FCShare chunk/backpressure engine.

Best for

Multi-gigabyte MP4/MOV files
Long phone recordings
Large editing exports
Live one-time delivery

What stays intact

Existing P2P/TURN behavior
Original available
Receiver-side direct save where supported
Live throughput-based ETA

Know before sending

No resumable transfer yet
Local media conversion depends on sender codec support
Destination free disk cannot be measured reliably
Both devices remain connected

Storage warnings are cautious

Browser quota is not the same as free disk. FCShare does not present fake exact disk-space numbers.

Transfer-time estimates improve after start

Before transfer, time is based on coarse network/path signals. Once bytes move, the normal FCShare progress calculation uses achieved throughput.

Questions people ask

Is there a FileCarpenter plan size cap?

No. Browser, device, storage and connection limits still apply.

Will it reduce video quality?

Not unless the sender explicitly chooses an available optimized variant.

Can TURN be used?

Yes. WebRTC may use an encrypted TURN relay when a direct path is unavailable.