How to Send Files to Someone Without Their Phone Number

A lot of modern sending assumes you already have the other person in your phone. WhatsApp wants a number. iMessage wants an Apple ID that is often a phone number. Nearby chat apps want a contact card before they will accept a PDF. That is a strange requirement when you only met someone at a meetup, a classroom, a client kickoff, or a family event and you just need to give them a file.

You can send photos, documents, and project folders without collecting a phone number and without adding a stranger to your address book. This guide covers room codes, email, cloud links, and in-person local transfer — plus the privacy habits that keep a one-time handoff from becoming a permanent contact you never wanted.

Why phone-number sharing became the default

Messaging apps grew around identity. A phone number is a stable handle, it maps to a SIM, and it makes spam slightly more expensive. For a one-time file, that identity layer is extra:

• You may not want them to message you next month
• They may not want you in their family group by accident
• International numbers and dual-SIM setups make "just WhatsApp it" fail
• The file may be larger than the chat app will take without compression

If the relationship is temporary, the transfer method should be temporary too.

Method 1: A room code instead of a contact card

A temporary room replaces "what is your number" with "enter this code." One person creates a space in the browser, reads the code aloud or writes it down, and the other person joins. Files and a short chat live in that space until it cleans up.

[PeerPizza](/) is one option in this pattern: no account, a room code, an optional PIN, browser-based access on phone or laptop, chat plus files, and rooms that auto-clean after inactivity. There is no fixed per-file size cap. You never type their number. They never type yours. Keep your own backup, because the room is not a shared drive you will reopen in October.

How to run the handoff in person

1. Open the site on your phone or laptop and create a room.
2. Optionally set a PIN if other people can hear the code.
3. Show them the code or spell it once. Do not post it to a public story.
4. They join on their own browser — any device is fine.
5. Upload the files. Use chat only for "this is the final PDF."
6. Wait until they say the download opened.
7. Leave. Expect automatic cleanup after inactivity.

This also works remotely if you already have any other channel (email, Slack, a classroom LMS) that can carry a six-character code. The code is not a phone number. It is a door key for one room.

Method 2: Email without turning it into a thread museum

Email still does not require a mobile number. If you have their address, attach a small PDF or send a link. Use a clear subject. Do not CC a dozen people "just in case." For large files, skip the attachment and send a room code or cloud link in the body so you do not bounce their corporate gateway.

If you do not have their email either, do not invent a fake one. Switch to a room code you can speak, or a QR they can open on the spot.

Method 3: Cloud links with tight permissions

A view-only link from storage you already use works when they need the file after today. Check three settings every time:

• Anyone with the link versus named accounts (named accounts need identity you may not have)
• Viewer, not editor
• Download allowed if the point is that they take a copy

Turn the link off when the event ends if the content should not live on the open web. A forgotten "anyone with the link" folder is how internal PDFs wander.

Method 4: Local transfer when you share a table

AirDrop, Quick Share, and a cable do not need a phone number. They need proximity and an accept tap. This is ideal for a conference hallway or a classroom desk. Confirm the file landed in their Downloads or Photos app before you walk to coffee. Local transfer also avoids putting the file on a third-party host at all.

Method 5: Shared work tools you already opened

If you are both in the same Notion page, Git host, classroom portal, or event Slack, put the file there. You are not collecting a number; you are using the space the gathering already created. Do not create a new WhatsApp group "for the files" if a portal already exists — that group will outlive the project and keep your number.

When you should still exchange a number

Collect a number when the relationship is the point: a real follow-up, a ride home, a hiring loop that will call. Do not collect a number as a poorly designed file-transfer protocol. Those are different jobs.

Privacy habits for people you just met

• Share the code narrowly. A code on a projector is public. A PIN on top of it helps.
• Do not upload more than they need. The extra folder of personal photos does not belong in a meetup handoff.
• Avoid identity documents on casual temporary tools.
• Assume the live window is visible to whoever has the code until cleanup runs.
• Keep your own backup. If they lose the download, you can send again. If you deleted the only copy, nobody can.
• Do not scan random QR codes that claim to be a file room. Type a known address or use a bookmark.

Temporary rooms that auto-clean after inactivity reduce leftover access. They do not make a bad audience safe.

Quality and completeness checks

Sending without a number only feels finished when they can open the file without texting you later — which they cannot do, because you never exchanged numbers.

• Watch them open the PDF or play the first seconds of the video
• Prefer original files over chat-style compressed images
• Name the file so it is findable in their Downloads list
• If there are several files, say how many they should see
• If a format is unusual (HEIC, Pages, a Linux tarball), say so before they leave

What this is not good for

• Long-running collaboration that needs comments next month
• Legal delivery that requires a tracked mailbox
• Secrets that belong in an encrypted, identity-checked channel
• Huge archives when both of you have weak mobile data and no Wi-Fi

Use the right heavier tool for those. A room code is for the gap between "we just met" and "we are in each other's phones."

Troubleshooting no-number file sends

They cannot join the room. Recheck the code, the PIN, and that they opened the same site. Search ads sometimes lead to lookalikes. Spell the code; do not rely on a photo of a screen in bad light.

They have no data. Switch to AirDrop, Quick Share, or a USB cable. A browser room needs a network path.

The download is a tiny preview. They saved a thumbnail or a chat compress. Resend as a real document or a room upload, not a photo of the first page.

Corporate Wi-Fi blocks the site. Try phone data, or fall back to email if an address exists, or write the files to a stick.

The room disappeared before they downloaded. Temporary rooms clean up after inactivity. Recreate and stay until they finish.

They want to message you later. That is a separate decision. Give a number, an email, or a professional profile — not a permanent WhatsApp group created only because a PDF needed a ride.

Comparison of ways to send without a phone number

A simple decision guide

• You are standing next to them, mixed phones: browser room or local share
• You have email only: email or a room code inside the email
• You have neither email nor number: speak a room code or use a local share
• They need the file next week: cloud link, not a room that will auto-clean
• You do not want a follow-up chat: do not collect a number just to send a PDF

Final thoughts

A phone number is a relationship. A file is a package. You can deliver the package without opening the relationship. Use a browser-based temporary room when you need a neutral space, email when you already have an address, local transfer when you share a table, and cloud links when the file must outlive the meeting. Keep your own copy, confirm they opened the download, and let rooms that auto-clean after inactivity do the goodbye for you. That is a calmer ending than a contact named "PDF guy from Thursday."