How to Install an eSIM from a Screenshot on One Device (2026 Step-by-Step Guide)

---

The Solo Traveler's Dilemma: Activating an eSIM Without a Second Screen

You have just stepped off a 12-hour flight at Narita or Heathrow. The airport Wi-Fi is spotty, immigration queues are surging, and you need mobile data immediately to hail a ride or confirm your transit itinerary. You open your confirmation email from your eSIM provider, only to be greeted by a crisp, square QR code staring back at you on the screen of the exact phone you are trying to activate.

For solo travelers, this creates a frustrating logistical paradox. The standard visual onboarding flow for consumer eSIMs was fundamentally designed around a two-device paradigm: display the QR code on a laptop, tablet, or printed sheet, and scan it with your phone’s rear camera. Without a companion’s screen to point your lens at, you are effectively trapped in a digital catch-22.

To understand why this happens—and how to bypass it—it helps to look under the hood of GSMA remote SIM provisioning.

`` +-------------------------------------------------------------------+ | SM-DP+ Server | | (Stores & encrypts carrier eSIM profiles) | +---------------------------------+---------------------------------+ | Encrypted Profile Download Over HTTPS | v +-------------------------------------------------------------------+ | Your Smartphone | | | | +-----------------------------------------------------------+ | | | LPA (Local Profile Assistant) | | | | • Decodes: LPA:1$smdp.provider.com$MATCHING_CODE | | | +-----------------------------+-----------------------------+ | | | | | APDU Security Channel | | | | | +-----------------------------v-----------------------------+ | | | eUICC (Embedded Secure Hardware) | | | | • Houses and runs digital SIM profiles | | | +-----------------------------------------------------------+ | +-------------------------------------------------------------------+ ``

The Architecture: Why eSIMs Rely on QR Codes

The QR code is not the eSIM profile itself; it is an encoded URI string that triggers an automated security handshake across three distinct layers:

1. eUICC (Embedded Universal Integrated Circuit Card): The tamper-resistant, dedicated security hardware chip soldered onto your device's motherboard.
2. LPA (Local Profile Assistant): The operating-system-level software agent (inside iOS or Android) responsible for requesting, downloading, and managing profile packages.
3. SM-DP+ (Subscription Manager Data Preparation): The carrier-side remote server that stores and encrypts the cellular profile.

When you scan an eSIM QR code, your device is simply reading a standardized GSMA string formatted as: LPA:1$smdp.example.com$ACTIVATION_CODE

The camera hands this string off to the LPA, which initiates a secure TLS handshake with the SM-DP+ server to install the cryptographic network keys directly into the eUICC.

Historically, mobile operating systems only allowed the LPA to be triggered via an active camera viewfinder. If the image lived inside your local photo gallery as a screenshot, the system had no native path to route that graphical payload into the LPA engine.

---

The 2026 Workaround Landscape

Fortunately, mobile operating systems and modern travel connectivity platforms have evolved to eliminate the need for a second screen. Today's travelers have four primary pathways to install an eSIM entirely on a single handset:

Modern travel data providers have begun bypassing the QR model altogether. Leading international providers like MollySIM utilize direct in-app API profile provisioning, allowing users to install an international profile straight to the eUICC with a single tap—no screenshots, scanning, or code manipulation required.

Furthermore, premium networks build safety nets directly into their data routing: while conventional budget eSIMs drop travelers down to an unusable 128kbps when high-speed allowances deplete, MollySIM maintains a 384kbps Fair Use Policy (FUP) baseline. This 3x speed advantage ensures critical logistics apps—such as Apple Pay token authentication, Uber pickups, and turn-by-turn Google Maps navigation—continue functioning seamlessly even if you run out of high-speed data while navigating transit terminals.

If your provider only sent a static QR code, however, the following step-by-step workflows will allow you to extract and install that profile directly from your device storage.

Step-by-Step: Installing an eSIM from a Screenshot on iPhone (iOS 17 & iOS 18+)

Apple’s neural engine and native optical character recognition (OCR) frameworks in iOS 17 and iOS 18+ allow users to provision an eSIM directly from a stored image file without using a second screen or physical printout.

Below are the two distinct iOS workflows to parse and execute the embedded carrier payload directly from your camera roll.

---

Method 1: Direct Long-Press via Live Text (Fastest)

Apple’s system-level Live Text engine automatically recognizes QR codes inside photos and isolates the encoded LPA:1$ activation string.

`` [ Screenshot Saved in Photos ] │ ▼ [ Tap & Hold on QR Code ] ───► [ System Menu: "Add eSIM" ] ───► [ Apple eUICC Provisioned ] ``

1. Capture the QR Code: Take a clean screenshot of the eSIM QR code provided by your carrier, ensuring the entire matrix code and surrounding borders are visible.
2. Open the Photos App: Navigate to your Camera Roll or Screenshots album and open the image full-screen.
3. Trigger Live Text: Press and hold your finger directly on the center of the QR code for 1–2 seconds.
4. Select “Add eSIM”: An iOS contextual menu will pop up directly over the image. Tap Add eSIM (or Set Up Cellular Service depending on your exact iOS sub-version).
5. Confirm Activation: A native modal will slide up from the bottom of the screen reading “Set Up Mobile Service”. Tap Continue to allow iOS to establish a secure handshake with the carrier's Remote SIM Provisioning (SM-DP+) server.

---

Method 2: System Settings via the Photo Picker

If Live Text fails to index the image automatically due to lighting, low contrast, or UI scaling, use the fallback camera roll picker embedded inside iOS Settings.

1. Go to Settings > Cellular (or Mobile Service).
2. Tap Add eSIM to launch the iOS cellular setup wizard.
3. Tap Use QR Code.
4. When the camera viewfinder appears, tap the Open Photos button located below the scan frame.
5. Select your saved screenshot. iOS will scan the frame, extract the activation payload, and immediately initiate carrier profile download.

---

Essential Post-Installation Settings for Travelers

Once your profile is installed into your device's eUICC chip, configure your SIM routing parameters to prevent unexpected roaming fees on your home line:

`` Settings > Cellular > [Your Travel eSIM] > Data Roaming ──► ON Settings > Cellular > Cellular Data > Allow Data Switching ──► OFF ``

---

Resolving iOS-Specific Setup Glitches

• "Unable to Complete Cellular Plan Change": This error typically indicates an interrupted handshake between iOS and the SM-DP+ server. Ensure you have a stable Wi-Fi connection during installation. If the issue persists, the single-use QR token may have already been consumed.
• "Code No Longer Valid": Most travel eSIM QR codes can only be scanned once. If the initial setup fails midway, verify in Settings > Cellular whether the profile is already listed under inactive SIM cards before attempting a re-scan.

To bypass manual screenshot scanning and iOS recognition errors entirely, providers like MollySIM offer 1-click in-app activation that pushes the profile directly to your iPhone's eUICC via native API. Furthermore, while typical travel eSIMs throttle users down to an unusable 128kbps once high-speed caps are reached, MollySIM’s 384kbps Fair Use Policy baseline keeps essential iOS features—such as Apple Pay transaction tokens, Uber dispatching, and Apple Maps routing—fully operational throughout your trip.

Android Walkthrough: Adding an eSIM from an Image on Samsung, Pixel, and Beyond

Unlike iOS, the Android ecosystem features slight UI differences across manufacturer skins (such as Samsung One UI, Google Pixel UI, and Xiaomi HyperOS). However, modern Android builds (Android 13, 14, and 15) allow you to scan an eSIM QR code directly from your device’s local storage without requiring a secondary screen.

---

Samsung Galaxy Devices (One UI 5.0, 6.0, and Newer)

Samsung provides the most frictionless native image-based eSIM onboarding on Android via a built-in gallery selector directly inside the system scanner.

`` Settings ──► Connections ──► SIM Manager ──► Add eSIM ──► Scan QR Code ──► Gallery Icon ``

1. Capture or save the eSIM activation QR code directly to your Samsung Gallery.
2. Open Settings and tap Connections.
3. Select SIM manager (or SIM card manager on older firmware).
4. Tap Add eSIM (or Add mobile plan).
5. When the camera viewfinder opens, tap the Gallery icon (located in the bottom-right corner of the viewfinder frame).
6. Select your saved screenshot from your albums. One UI will automatically isolate the matrix barcode, parse the LPA: string, and initiate the carrier download profile.
7. Tap Add / Confirm when prompted to install the plan.

---

Google Pixel Devices (Pixel 6, 7, 8, 9 Series)

Pixel UI handles eSIM installation under the unified network hub. While recent Pixel updates feature a direct gallery picker, older Android security patches may only display a live viewfinder.

Direct Method (Standard):

1. Navigate to Settings > Network & internet > SIMs.
2. Tap the + (Add) icon next to SIMs.
3. Tap Download a SIM instead? and hit Next.
4. When the camera activates, tap the Photo/Image icon next to the shutter to import your screenshot from Google Photos or Files.

Workaround via Google Lens (If the Gallery Icon is Missing):

If your carrier build or security patch omits the photo picker from the native scanner:

`` Google Photos ──► Open Screenshot ──► Google Lens ──► Copy LPA String ──► Pixel Setup: "Enter Manually" ──► Paste ``

---

Xiaomi, OnePlus, and Motorola UI Paths

For other prominent Android OEMs, follow these device-specific navigation routes to access the image-based QR scanner:

• Xiaomi / POCO (HyperOS / MIUI): Go to Settings > Mobile networks > Manage eSIM > Add mobile plan. Tap the system image browser icon within the camera frame to load your saved photo.
• OnePlus / OPPO (OxygenOS / ColorOS): Go to Settings > Mobile network > eSIM > Add eSIM. Tap Next, then tap the Album/Gallery icon at the top right of the scan interface.
• Motorola (MyUX): Go to Settings > Network & internet > Mobile network > Advanced > Carrier > Add carrier. Use the file browser prompt to feed the screenshot to the eUICC manager.

---

Troubleshooting Android-Specific Image Scan Errors

1. Android Scoped Storage & Gallery Permission Blocks

If tapping the gallery icon within the scanner fails to load your images or freezes the UI, your device’s security sandbox may be restricting the camera app from reading media storage:

• Go to Settings > Apps > All Apps.
• Locate the system camera or SIM Manager / eSIM Core Services.
• Select Permissions > Photos and videos (or Storage) and set it to Allow always or Allow all the time.

2. WhatsApp and Messaging Compression Artifacts

If a colleague or travel organizer sent your eSIM QR code via WhatsApp, Messenger, or Telegram, automatic image compression may degrade the matrix resolution, causing the scan algorithm to fail.

• The Fix: Request the QR code sent as an uncompressed document (.PDF or uncompressed .PNG). Alternatively, open the image, zoom in closely on the square QR code pattern, take a clean high-resolution crop screenshot, and scan that cropped version instead.

To bypass manual scanning, matrix compression issues, and Android LPA string extraction altogether, MollySIM allows direct digital profile installation via native Android carrier push. Once abroad, MollySIM’s built-in 384kbps Fair Use Policy baseline delivers three times the speed of industry-standard 128kbps throttles. This guarantees that data-heavy background services like Google Play authentication, Google Maps route recalculation, and live rideshare tracking stay completely dependable even if you exhaust your priority data allocation.

The Universal Fallback: Manual Setup with SM-DP+ Address & Activation Code

When optical recognition fails due to aggressive image compression, rendering glitches, or operating system sandbox restrictions, manual configuration serves as the ultimate failsafe. Every eSIM QR code is fundamentally a visual wrapper around an alphanumeric GSMA-standard string known as the LPA (Local Profile Assistant) Activation String.

By understanding how this string is structured, you can bypass image-parsing software entirely and inject the provisioning payload straight into your device’s secure baseband modem.

---

Deconstructing the eSIM LPA String Architecture

If you extract the raw text behind any carrier-generated eSIM QR code, you will encounter a standardized syntax structured like this:

``text LPA:1$smdp.provider.com$ABCD1234EFGH5678IJKL9012MNOP3456$1$CONFIRMATION_CODE ``

Understanding each delimited component prevents copy-paste errors:

`` ┌───────┬───┬─────────────────────────────┬──────────────────────────────────┬───┬───────────────────┐ │ LPA │ 1 │ smdp.provider.com │ ABCD1234EFGH5678IJKL9012MNOP3456 │ 1 │ CONFIRMATION_CODE │ └───────┴───┴─────────────────────────────┴──────────────────────────────────┴───┴───────────────────┘ │ │ │ │ │ │ │ │ │ │ │ └─ (Optional) Security PIN / Token │ │ │ │ └─ (Optional) Flag for Confirmation Code │ │ │ └─ Matching ID / Activation Code (32-char token) │ │ └─ SM-DP+ Address (Fully Qualified Domain Name) │ └─ Protocol Version (GSMA SGP.22 Specification) └─ Local Profile Assistant Prefix ``

• LPA:1$: The protocol header identifying the string as a GSMA-compliant remote SIM provisioning request.
• smdp.provider.com (SM-DP+ Address): The Subscription Manager Data Preparation server hostname responsible for storing and dispatching your encrypted eSIM profile.
• ABCD1234... (Activation Code / Matching ID): A unique, 32-character alphanumeric identifier that routes the remote server to your specific IMSI and cryptographic key bundle.
• Confirmation Code (Optional): A secondary PIN required by select enterprise or high-security networks (rarely used for travel data plans).

---

Step-by-Step: Copying & Pasting Manual Credentials

When manual configuration is required, separate the SM-DP+ Address and the Activation Code before navigating to your device settings.

`` +-----------------------------------------------------------------------------------------+ | MANUAL ENTRY CHEATSHEET | +-----------------------------------------------------------------------------------------+ | SM-DP+ Address: rsp.carrier.com | | (Do NOT include "https://" or trailing slashes) | | | | Activation Code: ABC1234-DEF567-GHI890-JKL123 | | (Paste only the unique 32-character Matching ID) | +-----------------------------------------------------------------------------------------+ ``

On iOS (iPhone 11 through iPhone 16 / 17 Pro):

1. Navigate to Settings > Cellular (or Mobile Data).
2. Tap Add eSIM.
3. At the bottom of the viewfinder screen, tap Use QR Code, then tap Enter Details Manually.
4. Paste the SM-DP+ Address into the first field (e.g., rsp.example-carrier.com). Ensure no whitespace was copied at the beginning or end.
5. Paste the Activation Code (Matching ID) into the second field.
6. Leave the Confirmation Code field empty unless explicitly provided by the provider.
7. Tap Next in the top-right corner to initiate the TLS handshake with the SM-DP+ server.

On Android (Google Pixel, Samsung Galaxy, Motorola):

1. Go to Settings > Network & internet > SIMs (or Connections > SIM manager on One UI).
2. Tap Add SIM / Add eSIM > Set up an eSIM.
3. Select Scan QR code from service provider.
4. Tap Enter code manually (or Need help finding your QR code? at the base of the screen).
5. Samsung One UI: Paste the discrete SM-DP+ and Activation Code into their respective fields.
6. Pixel / Pure Android: Pixel devices accept the full raw LPA string directly in one box:

LPA:1$smdp.provider.com$YOUR-MATCHING-ID-HERE

1. Tap Continue / Connect to register the SIM profile to your eUICC chip.

---

Method Comparison: Single-Device eSIM Activation

While manual fallback guarantees a path to connection even on heavily skinned Android forks, modern travel platforms remove the friction entirely. MollySIM bypasses the need to manage screenshots, scan QR codes on split screens, or isolate LPA parameters by using direct in-app carrier pushes.

Furthermore, once your profile is provisioned on the local network, MollySIM's built-in 384kbps Fair Use Policy baseline keeps essential travel infrastructure running smoothly. While standard travel eSIMs throttle down to 128kbps (which breaks modern encrypted handshakes), 384kbps provides 3x the bandwidth—ensuring that critical utilities like Apple Pay tokenization, Google Maps turn-by-turn routing, and WhatsApp text calls execute reliably even when high-speed allowances are exhausted.

Post-Installation Checklist, Network Troubleshooting, and the 384kbps Safety Net

Completing the optical or manual installation process registers the eSIM profile onto your device's embedded universal integrated circuit card (eUICC), but local network connectivity requires precise operating system configuration. Skipping the post-provisioning configuration can leave your device stuck in an offline state upon touchdown.

---

Phase 1: The Essential Post-Activation Configuration Checklist

Execute these three verification steps the moment you arrive in your destination country:

1. Toggle Data Roaming to "ON"

Travel eSIMs route data through international roaming partner agreements. Without roaming enabled, the device restricts the profile to local IMSI handshakes.

• iOS: Go to Settings > Cellular (or Mobile Data) > Select your new travel eSIM > Toggle Data Roaming to ON.
• Android: Go to Settings > Network & Internet > SIMs > Select the travel profile > Enable Roaming.

1. Verify the Access Point Name (APN)

While most modern profiles push APN payloads automatically via OMA-CP (Open Mobile Alliance Client Provisioning), certain custom Android skins require manual verification. If cellular data shows no throughput, inspect the APN field under your cellular profile settings and ensure it matches your provider's documentation exactly (typically lowercase, no spaces).

1. Designate Default Lines to Prevent Accidental Roaming Surcharges

To prevent your domestic carrier from billing you exorbitant daily roaming fees, set your primary domestic SIM to Calls & SMS Only and assign your new travel eSIM as the dedicated Cellular Data line. Disable Allow Cellular Data Switching on iOS to prevent automatic fallbacks to your home carrier.

---

Phase 2: Resolving Network Handshake & "No Service" Errors

If your device fails to establish an uplink within two minutes of landing, use the following technical matrix to diagnose and fix the bottleneck:

---

Phase 3: Surviving Zero-Balance Scenarios with the 384kbps FUP Safety Net

The most critical point of failure during international travel occurs when high-speed data allowances expire unexpectedly. In a foreign destination, running out of data while navigating remote areas, hailing a ride, or attempting to load a top-up webpage creates an immediate safety and logistical crisis.

`` Standard Travel eSIM Throttle: 64kbps – 128kbps (TLS Handshake Timeouts, Apps Fail) ══════════════════════════════════════════════════════════════════════════════════ MollySIM Continuous Baseline: 384kbps (Sustained SSL/TLS Integrity & Vector Loading) ``

Most conventional travel eSIMs impose severe Fair Use Policy (FUP) throttles down to 64kbps or 128kbps—bandwidth thresholds that instantly break modern web protocols due to TLS/SSL handshake timeouts. Under a 128kbps cap:

• Banking apps and digital wallets (Apple Pay, Google Wallet) fail cryptographic token verification.
• Ride-hailing platforms (Uber, Grab, Bolt) drop geolocation pings and fail to render maps.
• Browser sessions time out before rendering the eSIM provider's own recharge portal.

To eliminate this vulnerability, MollySIM implements an unmetered 384kbps safety net baseline across its data packages. Delivering 3x the throughput of legacy travel eSIM throttles, 384kbps provides the exact bandwidth floor required to maintain vital travel infrastructure:

• Real-Time Turn-by-Turn Navigation: Loads vector map tiles smoothly on Google Maps and Apple Maps without network timeout errors.
• Encrypted Communication: Maintains reliable connectivity for WhatsApp, iMessage, Signal, and Telegram text and VoIP voice calls.
• Mobility & Transit: Dispatches ride-hailing requests and updates live driver tracking coordinates in real time.
• Seamless Account Top-Ups: Keeps the provider app and self-care billing portals fully responsive, allowing you to add high-speed data without hunting for unsecured public Wi-Fi networks.

The Zero-Friction Future: Bypassing Screenshots with MollySIM 1-Click Activation

While saving QR codes to your camera roll and utilizing OS-level photo-scanning assistants resolves the "single-device installation" dilemma, it remains an interim workaround. Modern travel connectivity is shifting toward direct, native OS provisioning pipelines that completely eliminate intermediate image rendering, photo cropping, and manual SM-DP+ string copy-pasting.

Leading this technological shift, MollySIM integrates direct profile provisioning directly through its app. Rather than generating a static graphical QR matrix that requires secondary scanning, the platform communicates directly with your smartphone's Local Profile Assistant (LPA) to download and provision your carrier profile in a single background workflow.

`` [MollySIM In-App Checkout] │ ▼ (Encrypted Entitlement Token) [Native OS Profile Assistant / LPA] │ ▼ (Direct Cryptographic Handshake) [Device eUICC Hardware Chip] ──► Instant Network Registration ``

Direct In-App eUICC Provisioning: How 1-Click Installation Works

Direct provisioning leverages native mobile OS entitlement APIs (Apple’s CoreTelephony framework on iOS and the EuiccManager system service on Android). When you purchase a data package within the MollySIM app, the platform bypasses the traditional visual interface entirely:

1. Cryptographic Handshake: The app establishes an encrypted session with the Subscription Manager Data Preparation (SM-DP+) server, generating a dedicated eSIM profile bound to your hardware's unique EID (Embedded Identity Document).
2. System Prompt Invocation: The OS triggers a native system dialogue (e.g., "Add Cellular Plan" on iOS or "Download SIM" on Android) directly over the active application window.
3. Hardware Write: Tapping "Continue" instructs the LPA to write the IMSI and cryptographic profile directly onto the physical eUICC chip.

Seamless Roaming Across 150+ Countries with Persistent 384kbps Protection

Bypassing visual QR hurdles is only the first half of a reliable travel setup. Once provisioned via 1-click activation, MollySIM profiles provide instant access to Tier-1 local cellular networks across 150+ global destinations, automatically negotiating local breakout routing to minimize latency.

Crucially, this frictionless installation is backed by an automated connectivity safety net. If you exhaust your high-speed data tier while traveling:

• No Sudden Blackouts: Your line automatically drops to MollySIM's continuous 384kbps baseline instead of cutting off or falling to unusable 64kbps/128kbps limits.
• Preserved System Services: Because 384kbps maintains the necessary throughput for SSL/TLS handshakes, critical applications—including Google Maps vector rendering, Apple Pay token verification, Uber dispatch, and WhatsApp messaging—remain fully operational.
• Instant In-App Top-Ups: Because your connection never breaks, you can open the MollySIM app at any time to top up your high-speed allocation with zero reliance on open, unencrypted airport Wi-Fi networks.