How to transfer files between two computers over a local network
Transferring files over a local network is fast, private, and avoids upload limits of cloud services. This guide walks you through practical, step-by-step methods so you can move photos, documents, or large backups between two computers on the same LAN in minutes.
Step 1: Check network and connectivity
Ensure both computers are on the same router or Wi‑Fi SSID and can ping each other. Open a terminal or command prompt and run ping <other-computer-IP> for 4 packets; expect replies under 50 ms on a home network. If pings fail, verify firewall settings and cable/wireless connections before proceeding.
[Illustration: Two laptops connected to the same Wi‑Fi router with ping command output on screen]
Step 2: Decide transfer method
Choose a method based on file size and OS: SMB (Windows/Mac/Linux) for folders, SFTP for secure single-machine transfers, or a simple HTTP file server for one-off shares. For frequent large transfers (10 GB+), SMB or SFTP over gigabit Ethernet is fastest; for quick ad hoc sharing, use an HTTP server for a few minutes.
[Illustration: Icons representing SMB, SFTP, and HTTP with arrows between two computers]
Step 3: Prepare target folder and permissions
On the receiving computer, create a dedicated folder (e.g., C:\Shared\Incoming or /home/user/incoming) and set permissions to allow the sending account read/write access. On Windows grant Full Control to the user or Everyone for temporary sharing; on Linux use chmod 770 and chown to the receiving user to maintain security.
[Illustration: File explorer window showing a new Shared/Incoming folder with permission dialog open]
Step 4: Enable and configure SMB share
On Windows, right‑click the folder, choose Properties > Sharing > Advanced Sharing, enable share name, and set permissions. On macOS, enable File Sharing in System Preferences and add the folder; note the SMB address like smb://192.168.1.5. This method is ideal for multi-file transfers and folder syncing.
[Illustration: Screenshot mockup of folder share settings with network path displayed]
Step 5: Use SFTP or SCP for secure transfer
If one computer runs an SSH server, use scp or an SFTP client. From the sender run scp -r /path/to/files user@192.168.1.5:/home/user/incoming to copy recursively; expect roughly 80–110 MB/s on gigabit wired LAN. This is preferred for encrypted transfers and automation with scripts.
[Illustration: Terminal window showing scp command in progress with transfer rate indicator]
Step 6: Run a temporary HTTP file server
For ad hoc single-direction sharing, start a simple server on the sending machine: Python 3: python3 -m http.server 8000 in the folder to share. On the receiver open http://192.168.1.6:8000 in a browser and download files. This takes under 10 seconds to start and is convenient for users uncomfortable with network mounts.
[Illustration: Browser download page listing files from a local HTTP server with terminal command shown]
Step 7: Verify integrity and finalize
After transfer, compare file sizes and optionally checksums: on both machines run sha256sum filename (or Get-FileHash in PowerShell) and confirm identical hashes. When done, disable temporary shares or the HTTP server and reset firewall settings to maintain security.
[Illustration: Two screens showing file size comparison and matching sha256 checksums]
- Use wired gigabit Ethernet for large transfers to get 80–120 MB/s realistic throughput.
- Compress many small files into a single .zip or .tar.gz before transferring to reduce overhead and save time.
- When transferring >50 GB, initiate during off‑peak hours and allow 10–30 minutes per 10 GB on typical home networks.
- Map the SMB share as a network drive on Windows for drag‑and‑drop convenience and quicker repeat access.
- Use rsync over SSH for incremental backups; run rsync -avz /source/ user@host:/dest/ to speed up repeated syncs.
- Temporarily add a local user account on the receiver for secure direct transfers instead of opening shares to Everyone.
- Do not enable permanent Everyone access on SMB shares; restrict by user or disable after transfer to avoid exposing files on the LAN.
- Avoid running an HTTP file server on a public Wi‑Fi network; keep this method to trusted private networks only.
- Large transfers can saturate your network: schedule during low‑usage times to prevent disruption for other users.
- Verify that antivirus or endpoint protection is not blocking file transfer ports (22, 445, 8000) before changing firewall rules; improperly opening ports can create security risks.
Was this guide helpful?
More Computers & Electronics guides
How to set up Git, create a repository, and commit code locally
Setting up Git and committing code locally is a small, reliable skill that pays off immediately. In about 10–20 minutes you can install Git, create a repository, and make your first commits so your work is tracked and easy to manage. Follow these clear steps to get a solid local workflow going.
How to migrate email from one provider to another without losing folders or contacts
Migrating email between providers can feel risky, but with a plan you can preserve folders, labels, and contacts while minimizing downtime. This guide walks you through a careful, step-by-step transfer you can complete in a few hours to a couple days depending on mailbox size. Follow the checklist and you’ll keep structure and address data intact.
How to clean dust and replace a laptop fan to fix overheating and throttling
Overheating and CPU/GPU throttling are often caused by dust buildup or a failing fan. This guide walks you through safely cleaning dust and replacing a laptop fan to restore cooling performance and reduce temperature spikes. Read through all steps, gather basic tools, and work in a well-lit, static-safe area.