# Frequently asked questions

> Answers to common questions about Toss: limits, privacy, browsers and large files.

## Is Toss free?

Yes. There's no account, no subscription and no ads.

## Can I send files from Android to iPhone, or from my phone to my computer?

Yes. Toss works in any modern browser, so it moves files between Android phones (Samsung, Pixel, Xiaomi and others), iPhone and iPad, and Windows, Mac, Linux or ChromeOS computers, in any direction. Open the link on the sending device, or scan the QR code next to your link.

## Does my file go through your server?

No. Files travel directly between the two browsers over an encrypted WebRTC connection. When a direct path isn't possible, an encrypted relay forwards the data without being able to read it.

## How big can a file be?

There's no limit on our side. Very large files work best in Chrome or Edge on a computer, which save straight to disk. Other browsers, and phones, keep the file in memory until it's complete.

## How long does my link work?

For as long as you keep using Toss. Closing the tab or reloading doesn't change it. You can make a new link at any time; the old one stops working at once. An identity unused for 90 days is deleted, and its link stops working.

## What if I'm not online when someone sends me a file?

Their offer waits for up to 24 hours while their Toss tab stays open. As soon as you open Toss and accept, the file starts moving.

## Can several people send me files at once?

Yes. Everyone with the link can send you a file, and several transfers can run at the same time.

## Can the other person see my IP address?

Usually, yes: a direct connection between two browsers needs it. If the connection is relayed, they see the relay's address instead.

## What happens if I clear my browser data?

Your identity lives in your browser, so clearing site data gives you a new name and an empty list of recent connections. Identities unused for 90 days are also deleted from our server.

## How do I know the file wasn't changed on the way?

The WebRTC connection is encrypted end to end, and every file is checked with SHA-256 when it arrives. A damaged file is discarded.

Source: https://toss.appbits.dev/faq
