You have the file on an Android phone. The other person is holding an iPhone. AirDrop will not see you. Nearby Share will not see them. The first suggestion everyone makes is “just install this app,” which is exactly what neither of you wanted to do for a one-time send.
\nYou do not need a new icon on either home screen. A mobile browser, a short room or link, and a stable connection can move photos, videos, PDFs, and zips from Android to iPhone while keeping the original file. This guide covers the practical paths, the quality traps, and the phone-specific gotchas that actually stall transfers.
\nApple and Google built excellent local sharing inside their own walls. They did not build a friendly door between those walls.
\nCables do not save you either. There is no simple USB cable that mounts an Android phone on an iPhone. You would need a computer in the middle. For a hallway handoff, that is ridiculous. Browser-based sharing exists because the two phones already share one thing: a modern web browser.
\nThe lowest-friction no-app path is a temporary web room. Both people open the same site in Chrome, Safari, Firefox, or Samsung Internet. One person creates a room. The other joins with a code.
\n[PeerPizza](/) is built around that pattern: no account, a room code, an optional PIN, chat plus files in the same space, and temporary rooms that auto-clean after inactivity. There is no fixed per-file size cap, though a phone’s memory, browser tab, and network still decide what is realistic. Keep your own backup. When the room goes quiet, it is supposed to disappear.
\nYou can also start the room on the iPhone and upload from Android. Direction does not matter. The browser is the bridge.
\nIf one of you already lives in Google Drive, iCloud, Dropbox, or OneDrive, a share link still works without a new app, as long as the mobile browser can open the host.
\nThis is better when the file must stay available for hours after you stop looking at your phone. It is worse when Drive is full, the iPhone user does not want to sign in, or you only needed a ten-minute handoff.
\nIf both of you already have WhatsApp, Telegram, Signal, or similar, you can stay in the app you already installed. That is not a new app. It is still a quality minefield.
\nDefault photo send on most chat apps recompresses the image. That is why a sharp Android camera photo arrives on iPhone looking soft. Document mode usually skips that pipeline. If quality is the whole point, skip chat and use a full-file room or cloud download instead.
\nEmail works when the file is under the attachment cap, commonly around 25 MB on Gmail. For a PDF or a couple of photos, it is fine. For a video, it usually is not. If the mail app offers to insert a Drive link, you are back in Method 2, with the same permission questions.
\nAndroid and iPhone do not store media the same way.
\nAlways compare file size after download to the size on the Android phone. If the iPhone copy is dramatically smaller, you sent a compressed chat version by mistake.
\nThe iPhone cannot find the file after download. Look in Files > Downloads, not only in Photos. Safari does not always file media into the camera roll.
\nUpload sits at 0% on Android. The browser may lack storage permission, or the file is in an app sandbox the picker cannot see. Share or export the file to Downloads first, then pick it again.
\nThe room code does not work. Codes are easy to mistype on a phone keyboard. Resend it as text, confirm any PIN, and make sure both people opened the same site.
\nThe transfer dies when the screen locks. Enable Auto-Lock / Screen timeout to a longer value, or keep a thumb on the screen. Plug in both phones.
\nPublic Wi-Fi seems connected but nothing moves. Cafes and campuses often isolate clients. A browser room that relays over HTTPS can still work when local device-to-device discovery fails. If the portal is captive, complete the sign-in page first.
\nThe photo looks fine on Android and soft on iPhone. You probably sent it as a chat image. Resend as a document or through a full-file room and compare byte sizes.
\niPhone says the video cannot be played. The codec may be unusual. Ask them to open it in Files with a player, or export an H.264 MP4 from Android if compatibility matters more than maximum efficiency.
\n| Method | New app? | Quality | Typical snag | Best for |
|---|---|---|---|---|
| Temporary web room | No | Original file | Screen sleep mid-upload | One-time photos, video, PDFs |
| Existing cloud link | No, if the website works | Original if they download | Login or quota | Files that must stay up longer |
| Chat document mode | No, if already installed | Usually original | Size caps, easy to pick “photo” by mistake | Small files to an existing contact |
| Email attachment | No | Original | About 25 MB | Tiny PDFs |
| AirDrop / Nearby Share | Built-in, wrong platform | Original | Does not cross Android and iPhone | Same-ecosystem only |
Android and iPhone will not AirDrop to each other. That is not your fault, and it does not require a new app. Open a browser on both phones, share a room code, move the original file, and save it on the iPhone in Files or Photos. Confirm the download, keep your own backup, and let the temporary room disappear. That is the whole trick: use the one piece of software both phones already agree on.
","content_text":"You have the file on an Android phone. The other person is holding an iPhone. AirDrop will not see you. Nearby Share will not see them. The first suggestion everyone makes is “just install this app,” which is exactly what neither of you wanted to do for a one-time send.\n\nYou do not need a new icon on either home screen. A mobile browser, a short room or link, and a stable connection can move photos, videos, PDFs, and zips from Android to iPhone while keeping the original file. This guide covers the practical paths, the quality traps, and the phone-specific gotchas that actually stall transfers.\n\nWhy Android to iPhone is awkward\n\nApple and Google built excellent local sharing inside their own walls. They did not build a friendly door between those walls.\n\n- AirDrop uses Apple’s mix of Bluetooth discovery and Wi-Fi Direct. Android is not invited.\n- Nearby Share / Quick Share is Google’s answer. iPhone is not invited.\n- iMessage does not exist on Android.\n- Chat apps work on both, then quietly compress photos and videos unless you fight the defaults.\n\nCables do not save you either. There is no simple USB cable that mounts an Android phone on an iPhone. You would need a computer in the middle. For a hallway handoff, that is ridiculous. Browser-based sharing exists because the two phones already share one thing: a modern web browser.\n\nMethod 1: A temporary room in both browsers\n\nThe lowest-friction no-app path is a temporary web room. Both people open the same site in Chrome, Safari, Firefox, or Samsung Internet. One person creates a room. The other joins with a code.\n\nPeerPizza is built around that pattern: no account, a room code, an optional PIN, chat plus files in the same space, and temporary rooms that auto-clean after inactivity. There is no fixed per-file size cap, though a phone’s memory, browser tab, and network still decide what is realistic. Keep your own backup. When the room goes quiet, it is supposed to disappear.\n\nStep-by-step from Android to iPhone\n\n1. On the Android phone, open Chrome or your default browser and create a room.\n2. Copy the room code. If the file is private, set a PIN.\n3. Send the code (and PIN) in a normal text, not a public story.\n4. On the iPhone, open Safari or Chrome, enter the code, and join.\n5. On Android, pick files from Photos, Files, or Downloads. Prefer the original item, not a screenshot of the photo.\n6. Keep both screens awake until the upload and download finish.\n7. On the iPhone, tap download and save to Files or Photos, depending on the type.\n8. Confirm the saved file opens. Then you can leave. The room will clean itself up later.\n\nYou can also start the room on the iPhone and upload from Android. Direction does not matter. The browser is the bridge.\n\nMethod 2: Cloud links you already have\n\nIf one of you already lives in Google Drive, iCloud, Dropbox, or OneDrive, a share link still works without a new app, as long as the mobile browser can open the host.\n\n- Upload from Android in the Drive or Dropbox website if you do not want the native app.\n- Set permission so the iPhone user can download, not only preview.\n- On iPhone, open the link in Safari and use Download or Share to Files / Photos.\n\nThis is better when the file must stay available for hours after you stop looking at your phone. It is worse when Drive is full, the iPhone user does not want to sign in, or you only needed a ten-minute handoff.\n\nMethod 3: Chat apps, but only in document mode\n\nIf both of you already have WhatsApp, Telegram, Signal, or similar, you can stay in the app you already installed. That is not a new app. It is still a quality minefield.\n\n- Send the item as a document / file, not as a gallery photo or video.\n- Check the size limit for that app. A long 4K clip may still be too large.\n- Tell the iPhone user to save the downloaded file, not to rely on the chat bubble preview.\n\nDefault photo send on most chat apps recompresses the image. That is why a sharp Android camera photo arrives on iPhone looking soft. Document mode usually skips that pipeline. If quality is the whole point, skip chat and use a full-file room or cloud download instead.\n\nMethod 4: Email, only for small files\n\nEmail works when the file is under the attachment cap, commonly around 25 MB on Gmail. For a PDF or a couple of photos, it is fine. For a video, it usually is not. If the mail app offers to insert a Drive link, you are back in Method 2, with the same permission questions.\n\nAndroid-side tips that prevent failed uploads\n\n- Use the system picker. Recent files, Downloads, and Photos are the usual sources.\n- If the file lives inside a manufacturer “My Files” app, note the folder before you start.\n- Turn off battery restrictions for the browser if uploads die the moment the screen dims.\n- Prefer Wi-Fi. Cellular uploads of large video burn data and drop more often.\n- Disable Low data mode or Data saver for the Wi-Fi network if the transfer crawls.\n- Upload in batches if the browser becomes sluggish with a huge multi-file selection.\n\niPhone-side tips that prevent “I got nothing”\n\n- Safari may ask for download permission. Allow it for the site you intended to use.\n- Videos and PDFs often land in the Files app, not in Photos. Check Downloads there.\n- HEIC photos from some Androids, or JPEG from some iPhones, can confuse the other gallery. If they cannot open it, export a widely compatible JPEG or MP4.\n- Keep Safari in the foreground. iOS is aggressive about sleeping background tabs.\n- If Photos does not import a downloaded image, open Files and use Share > Save to Photos.\n\nQuality and format issues between the two phones\n\nAndroid and iPhone do not store media the same way.\n\n- Photos: iPhone still leans HEIC. Many Android cameras shoot JPEG or a brand-specific format. If the iPhone Photos app will not import the file, save it in Files first or export JPEG on the Android side.\n- Video: 4K HEVC from either phone may need a player the other OS already has. Sending the original file is still better than letting a chat app transcode it to a muddy 720p preview.\n- Documents: PDF is the safest cross-platform document. Office files usually open, but fonts and layout can shift. When layout matters, send PDF.\n\nAlways compare file size after download to the size on the Android phone. If the iPhone copy is dramatically smaller, you sent a compressed chat version by mistake.\n\nTroubleshooting Android-to-iPhone browser transfers\n\nThe iPhone cannot find the file after download. Look in Files > Downloads, not only in Photos. Safari does not always file media into the camera roll.\n\nUpload sits at 0% on Android. The browser may lack storage permission, or the file is in an app sandbox the picker cannot see. Share or export the file to Downloads first, then pick it again.\n\nThe room code does not work. Codes are easy to mistype on a phone keyboard. Resend it as text, confirm any PIN, and make sure both people opened the same site.\n\nThe transfer dies when the screen locks. Enable Auto-Lock / Screen timeout to a longer value, or keep a thumb on the screen. Plug in both phones.\n\nPublic Wi-Fi seems connected but nothing moves. Cafes and campuses often isolate clients. A browser room that relays over HTTPS can still work when local device-to-device discovery fails. If the portal is captive, complete the sign-in page first.\n\nThe photo looks fine on Android and soft on iPhone. You probably sent it as a chat image. Resend as a document or through a full-file room and compare byte sizes.\n\niPhone says the video cannot be played. The codec may be unusual. Ask them to open it in Files with a player, or export an H.264 MP4 from Android if compatibility matters more than maximum efficiency.\n\nComparison: no-new-app ways to go Android to iPhone\n\n| Method | New app? | Quality | Typical snag | Best for |\n| :--- | :--- | :--- | :--- | :--- |\n| Temporary web room | No | Original file | Screen sleep mid-upload | One-time photos, video, PDFs |\n| Existing cloud link | No, if the website works | Original if they download | Login or quota | Files that must stay up longer |\n| Chat document mode | No, if already installed | Usually original | Size caps, easy to pick “photo” by mistake | Small files to an existing contact |\n| Email attachment | No | Original | About 25 MB | Tiny PDFs |\n| AirDrop / Nearby Share | Built-in, wrong platform | Original | Does not cross Android and iPhone | Same-ecosystem only |\n\nA simple decision guide\n\n- A few photos or a PDF, right now: temporary browser room.\n- A video you care about: same, and stay on Wi-Fi with both screens awake.\n- They will download tonight, not this minute: cloud link with download permission.\n- You already chat every day and the file is small: document mode, not the gallery picker.\n- You are both next to a laptop: use the laptop as a bridge if the phones keep failing.\n\nFinal thoughts\n\nAndroid and iPhone will not AirDrop to each other. That is not your fault, and it does not require a new app. Open a browser on both phones, share a room code, move the original file, and save it on the iPhone in Files or Photos. Confirm the download, keep your own backup, and let the temporary room disappear. That is the whole trick: use the one piece of software both phones already agree on.","word_count":1692,"author":{"name":"Vishvajeet Shukla","url":"https://vishvajeetshukla.in","same_as":["https://vishvajeetshukla.in","https://twitter.com/vishu_07","https://x.com/vishu_07"]},"seo":{"canonical":"https://peerpizza.vercel.app/blog/share-files-android-to-iphone-without-app"},"citation_policy":{"attribution_required":true,"link_back_required":true,"canonical_field":"url"}}