The short answer
Identify whether pairing, direct connection, file reading or saving failed. Keep one current code and both pages open, then test a single identifiable file before a large batch.
Open the free toolIdentify the stage that has failed
Separate four observations before restarting: whether the computer shows a code, whether the phone opens its link, whether the devices report a connection and whether a chosen file appears at the receiver. These are different stages. For an illustrative failure report, write “phone opens the page but computer is still waiting” rather than “photos broken”. The exact visible message matters more than how long the attempt felt. Preserve any received files before closing either page, because restarting a connection is not a way to save content already held by the receiving tab.
Keep one current pairing in view
Start on the intended receiving computer and scan the code currently displayed there. An old screenshot or copied link may refer to an expired or replaced pairing. “New code” deliberately makes the previous code unusable. After creating one, scan that new code instead of retrying an old message on the phone. Keep the code page open while the other device joins. If several computers or browser tabs are involved, choose one pair and identify them clearly. A successful connection to a different tab can look like missing files on the screen you are watching.
Distinguish an unopened link from a blocked connection
If scanning does not open the transfer page, first check what the camera actually recognised and whether the browser followed the offered link. “Copy link” provides another route for your own device when scanning is inconvenient. Keep the full private link intact and share it only with the intended device. Do not publish it in a public chat while asking for help. Possession of the pairing link permits joining that session; local processing of photo bytes does not make a disclosed link harmless. You can describe the visible error without exposing its secret.
Read the connection-service message
The page can load while the service used to arrange pairing is temporarily unreachable. A message that the service is not answering is different from a direct-path failure after pairing. Confirm ordinary connectivity on both devices and read the current status instead of repeatedly selecting photo batches before a connection exists. The service passes encrypted connection messages; the selected files themselves take the direct device connection. Knowing those separate roles prevents a misleading conclusion that a pairing problem means the photos have already been uploaded somewhere or lost inside a cloud folder.
Try an allowed network path
The browsers need a direct WebRTC connection. Some guest, school or company networks prevent the devices reaching each other, and a VPN can change the available route. Where permitted, put the two devices on the same trusted network and retry the pairing. Follow the rules for managed equipment instead of bypassing a required configuration. Photo Transfer provides no relay fallback for a blocked direct path. Sharing Wi-Fi is a useful diagnostic simplification, not proof that every router configuration will permit the connection or a guarantee of transfer speed.
Keep the phone and its page active
A phone can suspend a browser tab when the screen locks or another app takes over. Keep both pages visible during the small test transfer and read whether the session actually remains connected. If the connection ends, preserve received files first, then use the displayed reconnect route or show the code again on the host. Do not count a queued filename as a finished received file. A long camera recording may expose a suspension problem that a small photo did not, so avoid treating one successful preview as a guarantee for an unattended batch.
Check whether the sender can read the selected file
A file-selection error is not necessarily a network failure. A picture visible in the phone's library may need to become available on that device before the browser can read it. Follow the message and select the item again, or save an available local copy first. Begin with one clearly identifiable small file to distinguish a reading problem from connection setup. Check the exact failed filename when other files in the group succeeded. Re-pairing the same devices repeatedly will not fix an item the sender cannot supply to the browser.
Verify saving after the connection works
Once a file appears at the receiver, use “Save” or an appropriate group-saving control and open the independent download. A received HEIC that Windows cannot display is a format-viewing issue, not automatic evidence of a failed connection. The tool sends the supplied file without converting it to JPG. Record the saved extension and use a separate conversion when necessary. Keep the source until the required copies are verified. A successful transfer and a successful save are distinct checks; neither is an automatic backup of the whole phone library.
Questions you might still have
The phone opened the page, so why is the computer waiting?
Opening a link is one stage; joining and establishing a direct path are later ones. Check that it is the current pairing and read both status messages. Keep the host page open and avoid mixing an old link with a new code.
Can I reuse a screenshot of yesterday's code?
Use the code currently offered by the host. Pairing can expire, and creating a new code invalidates the earlier one. A screenshot is not a permanent address for that computer. Start or resume the intended session and scan its live code.
Does the same Wi-Fi guarantee connection?
No. It simplifies the path, but network isolation or other configuration can still prevent direct access. Try an allowed trusted route and read the resulting error. The tool has no relay that automatically carries files around a blocked direct connection.
Why did only one selected photo fail?
Check whether that item can be read on the sending device and note its name. A cloud-library entry may need to be made available first. When other items arrive, investigate the failed selection instead of assuming the entire pairing must be rebuilt.
Should I send the pairing link in a support message?
Describe the error without exposing the private session link. Someone who receives the link can try to join its pairing. Keep it limited to the intended devices and generate a new code if you need to replace a disclosed one.
Why is a saved photo unreadable after a successful transfer?
Inspect its actual format. Direct transfer does not make HEIC into JPG or install a viewer on Windows. Verify the saved file and use a separate suitable format conversion where needed; resending identical bytes will not add the missing format support.
Sources & useful details
These guides are written from the current LoschaZ tools and the sources listed above. Examples are illustrations, not tests on every device or promises of an identical result.
