How to Use Copyparty: The Beginner's Guide (First Share, the QR Code, Accounts, and the Internet-Exposure Rule)

CodexFuse Team · 2026-11-01T14:43:57.592Z · 15 min read

Copyparty is a single Python file that turns any folder into a browser file server. This beginner's guide walks you through your first share, the QR-code phone transfer, accounts, the config file, Docker, and the internet-exposure rule.

How to Use Copyparty: The Beginner's Guide (First Share, the QR Code, Accounts, and the Internet-Exposure Rule)

Learning how to use Copyparty is the fastest way to stop emailing files to yourself: it is a single Python file that turns any folder on your computer into a file server you open in a browser — no install wizard, no account, no cloud service in the middle. You download one file, run it, and your laptop starts serving files on port 3923 while the terminal prints a QR code your phone can scan to browse and upload instantly. This Copyparty tutorial runs the complete beginner arc: the one-file install, your first share, the QR-code phone transfer, accounts and passwords, the config file, resumable uploads, media streaming, WebDAV, Docker, and the internet-exposure rule that keeps the whole thing safe.

The quickest start needs nothing but Python — but the safest way to run it permanently is inside a container, so if that world is new to you, read the Docker beginner guide before the Docker section below. Copyparty's sibling for moving files between cloud drives is a different tool entirely: read the Rclone beginner guide for the cloud-sync lane — Rclone moves files between remotes, Copyparty serves them to humans.

What is Copyparty?

Copyparty is a portable, open-source file server written in Python that turns any folder on your machine into a shareable website: files become browsable, searchable, streamable, and uploadable through an ordinary browser, with no client software needed on the other end. The entire program ships as one self-contained file — copyparty-sfx.py — that runs on Python 2.7 or 3.3 and newer, so the "install" is a download and nothing else. It speaks HTTP, WebDAV, FTP, FTPS, TFTP, SFTP, and SMB/CIFS, which means the same server that shows your phone a clean web page can also give your desktop apps a mounted network drive.

How do you use Copyparty?

You use Copyparty by running the single-file program on the machine that holds the files, then opening its address — or scanning its QR code — from any device on the same network. The whole beginner path is eight steps:

1. Download copyparty-sfx.py from the official GitHub releases page (the releases/latest/download link below is the canonical always-current URL, verified 2026-11-01; the project tracks the 1.20.x line).
2. Create one dedicated share folder — never your whole home directory — and change into it.
3. Run python copyparty-sfx.py and watch the terminal print your LAN address, port 3923, and a QR code.
4. Open http://your-pc-ip:3923 in a browser on the same Wi-Fi, or scan the QR code with your phone.
5. Browse, stream, and upload through the web interface — big uploads resume automatically if the connection drops.
6. Add your first account with -a you:strongpassword so the share stops being open to everyone on the network.
7. Graduate to a config file (copyparty.conf) with named volumes and per-user permissions.
8. Set the exposure boundary: LAN-only is fine as-is; anything beyond the LAN needs accounts plus HTTPS, a reverse proxy, or a tunnel — raw port 3923 never faces the public internet.

How do you install Copyparty?

Installing Copyparty is a download, not an installation, because the program is one self-contained Python file — the whole copyparty install takes about sixty seconds on any machine with Python. Get the current build with:

curl -L https://github.com/9001/copyparty/releases/latest/download/copyparty-sfx.py > copyparty-sfx.py
python copyparty-sfx.py

That releases/latest/download URL is the canonical link that always serves the newest release — it was verified current at write time (2026-11-01), when the project was on the 1.20.x line and the Arch Linux package tracked 1.20.26, built 2026-10-20. The sfx file runs on Python 2.7 or Python 3.3 and newer, so practically any machine from the last decade can run it. Linux and macOS users also get copyparty-sfx.sh; Windows users get copyparty.exe, a standalone binary that needs no Python at all. If you prefer a package manager, pip install copyparty pulls the same program from PyPI.

What happens when you run Copyparty for the first time?

Running python copyparty-sfx.py with no arguments starts a server on port 3923 that shares your current folder — and here is the part worth saying loud: it is completely open. Everyone on your network gets read and write access to that folder, with no password and no login screen. That is a deliberate design choice for five-minute local tests, not an accident, and the vendor documents it plainly. So the first-run ritual is: make a dedicated folder for the share, change into it, and only then launch. The terminal prints the machine's LAN IP addresses, the port, and a QR code encoding the server URL; any device on the same Wi-Fi opens the page in a browser or scans the code. The web interface is the whole experience — file browser, upload buttons, media player, search, and even copy-paste WebDAV mount commands for your platform.

How do you transfer files from your phone to your PC over Wi-Fi?

This is the move that kills the email-files-to-yourself habit and solves the classic "share files without usb" problem: start Copyparty in the folder you want on your PC, scan the copyparty qr code in its terminal with your phone's camera, and your phone opens the share directly in its browser. From there you upload photos and videos straight from the camera roll into the PC's folder — no USB cable, no cloud storage, no account on either end. Downloads run the same direction: tap a file on the phone and it saves locally. The transfer never leaves your Wi-Fi network, which is why this phone to pc file transfer wifi flow is faster than a cloud round-trip and private by construction. That phone-to-PC hop is the single most popular Copyparty use case in every tutorial written about it.

How do you add accounts and passwords to Copyparty?

You add accounts with the -a flag: python copyparty-sfx.py -a you:strongpassword creates a user named you, and the open-to-everyone default disappears behind a login the moment any account exists. For anything permanent, accounts belong in the [accounts] section of the config file, where passwords can be stored with Argon2 hashing instead of sitting in your shell history. Anonymous visitors lose access automatically unless a volume explicitly grants it — which is exactly the lever the permission system uses to build public and private areas side by side.

How does the Copyparty config file work?

The config file turns the one-liner into a real server: launch with -c party.conf and Copyparty reads three kinds of sections. [global] holds server-wide settings such as the port (p: 3923) and behavior flags; [accounts] holds users and their password hashes; each [/url-path] section maps one URL path to one folder on disk plus an accs: block of per-user permissions. The volume rule beginners get wrong is simple: bind one dedicated folder per volume — never your whole home directory — because every permission you grant applies to everything underneath that path. Here is the shape of a minimal config (adapted from the documented format; run copyparty -h and the official wiki for the exact schema at your version):

[global]
  p: 3923

[accounts]
  ed: $argon2-hashed-password

[/photos]
  /home/ed/share/photos
  accs:
    r: *
    w: ed

The [/photos] section says the URL path /photos serves the folder /home/ed/share/photos; the accs: block says everyone (*) may read while only ed may write. The same volumes can be declared on the command line with -v src:dst:perm syntax, which is handy for quick tests before you commit to a file.

What do Copyparty's permission letters mean?

Copyparty permissions are single letters stacked per user, and the whole access model fits in one table:

The clever documented pattern is the dropbox volume: grant w to everyone but withhold r, and strangers can drop files in without ever seeing what is already there — the vendor recommends exactly this shape for public upload boxes. Combine it with accounts and you get the classic setup: a public read-only gallery, a dropbox for submissions, and a private admin area, all from one config file.

How do resumable uploads work in Copyparty?

Copyparty's uploader splits large uploads into chunks and tracks which pieces already arrived, so a dropped Wi-Fi connection resumes from the interruption instead of restarting the file. The release notes for the 1.20.x line even fixed resuming partial uploads after a server restart, which shows how seriously the project takes interrupted transfers. Practically, this means a 4 GB video survives a flaky network: the progress bar picks up where it stopped instead of going back to zero. The rule of thumb is to use the web uploader for anything over a few hundred megabytes, because chunking is where the resume behavior lives — a plain single-shot form post cannot do this.

Can Copyparty stream music and video?

Yes — open an audio or video file in the Copyparty web UI and it plays directly in the browser, no download required. Thumbnails and audio/video transcoding come with the ffmpeg-bundled Docker image (copyparty/ac), which is the easy way to get them without installing ffmpeg yourself. The browser player plus resumable uploads is the combination that makes Copyparty a credible personal media shelf: upload a movie once from your PC, stream it to your phone on the couch. Media-tag indexing via the -e2ts flag can catalog a music collection by artist, album, and title.

How do you use Copyparty with WebDAV?

Every Copyparty volume doubles as a WebDAV endpoint, so you can mount a share as a network drive in your operating system and move files with your normal file manager instead of a browser. The copyparty webdav endpoint for a volume is simply its normal URL, and the web UI shows copy-paste mount commands for your platform; on Windows you use "Map network drive" with the volume URL, on macOS Finder → Go → Connect to Server, on Linux your file manager's "Connect to Server" or davfs2. Power users pair WebDAV with Rclone, because Rclone's transfers are faster and scriptable than a file-manager drag — the Rclone beginner guide covers the remote-side setup, and the inkyvoxel Copyparty guide documents exactly this pairing for bulk uploads. One warning carries over: authenticate first, because a WebDAV mount with no password is the open-share problem wearing a fancier hat.

What protocols does Copyparty support?

Copyparty is a multi-protocol server, and each protocol serves a different kind of client:

The exact enable-flags and ports for each protocol move between versions, so treat copyparty -h as the authoritative reference at your version rather than memorizing a flag list from any tutorial.

How do you run Copyparty in Docker?

Docker is the permanent-home lane for Copyparty: the container isolates the server from your host and makes the data volumes explicit. The copyparty docker images come in a small family, and the choice is really about how much media processing you want inside the container:

Two further variants, copyparty/iv and copyparty/dj, exist for specialized builds. The quick-start for the recommended image is:

docker run --rm -it -u 1000 -p 3923:3923 \
  -v /mnt/nas:/w -v $PWD/cfgdir:/cfg copyparty/ac

Note the honest catch: Docker adds isolation, not security — with no config file in /cfg this container shares /w read-write with anyone, exactly like the bare sfx. Put your party.conf in the /cfg mount and add hist: /cfg/hists/ under [global] so the upload-history database stays out of your shared folders. If Docker itself is new to you, the Docker beginner guide explains what those volume flags are doing before you run this.

What is the internet-exposure rule for Copyparty?

The internet-exposure rule is the one sentence that keeps a Copyparty server safe: the zero-configuration launch is a five-minute local test — anything reachable beyond your LAN must sit behind accounts plus HTTPS, a reverse proxy with its own authentication layer, or a secure tunnel. Raw HTTP port 3923 must never face the public internet, full stop. The project ships reverse-proxy configs in its repo (including a documented nginx example), and Caddy setups are documented in the wild. For remote access without opening any inbound port at all, Tailscale is the safe lane: every device gets a stable private address inside your own tailnet, so your phone reaches the server from anywhere with zero port-forwarding — read the Tailscale beginner guide for that setup. Raw port-forwarding on your router is the last resort, not the plan.

Copyparty vs Rclone vs Filebrowser: which one do you need?

These three get confused because they all move files, but they do different jobs — pick by the job, not the hype:

They compose rather than compete: Rclone can feed files into the folders Copyparty serves, and Filebrowser suits teams that want managed accounts where Copyparty suits anyone who wants a share running in sixty seconds.

What are the 7 mistakes every Copyparty beginner makes?

Sources

• XDA Developers — "I set up Copyparty and never need to email files to myself again" (the LAN-share arc: one Python file, port 3923, QR code in the terminal) — https://www.xda-developers.com/set-up-copyparty-never-email-files-again/
• Tom's Hardware — "How to transfer and share files over a network without a USB flash drive — and with just one line of code" (the one-line quick-share arc, browser media playback) — https://www.tomshardware.com/software/how-to-transfer-and-share-files-over-a-network-without-a-usb-flash-drive-and-with-just-one-line-of-code
• WindowsForum — "Copyparty on Windows 11: Secure File Server Setup, Docker, WebDAV and rclone" (2026-10-18; the Windows secure-setup piece: config file, accounts, Docker image family and sizes, the internet-exposure guidance) — https://windowsforum.com/news/copyparty-on-windows-11-secure-file-server-setup-docker-webdav-and-rclone.448985/
• inkyvoxel — "Setting up Copyparty on a home server" (Caddy reverse proxy plus systemd, WebDAV paired with rclone for bulk uploads) — https://www.inkyvoxel.com/setting-up-copyparty-on-a-home-server/
• Copyparty on PyPI — install one-liner, default-open behavior, account flag, volume and permission syntax — https://pypi.org/project/copyparty/
• Copyparty GitHub releases — release artifacts (sfx, exe), the read-only demo, the dangerous-build warning — https://github.com/9001/copyparty/releases
• Wikipedia — Copyparty (software) — protocol list, version history — https://en.wikipedia.org/wiki/Copyparty_(software)
• Arch Linux package database — copyparty 1.20.26-1, built 2026-10-20 — https://archlinux.org/packages/extra/any/copyparty/
• Runpod community docs — CopyParty file manager (GPU-instance file management) — https://docs.runpod.io/community-solutions/copyparty-file-manager/overview

Frequently Asked Questions

Is Copyparty free?

Yes. Copyparty is free and open-source software by the developer known as 9001, and every feature — the web UI, WebDAV, FTP, accounts, Docker images — ships in the free build. There is no paid tier, no account to create, and no telemetry phoning home. The only costs you might ever pay are your own: the machine it runs on and the storage it serves.

Is it safe to expose Copyparty to the internet?

Not in its default state. A fresh launch is intentionally open to everyone on the network, which is fine for a five-minute LAN test and dangerous anywhere else. Safe internet exposure means accounts with strong passwords, HTTPS via a reverse proxy, and ideally an extra authentication layer or a private tunnel in front of it. Never publish raw HTTP port 3923 to the public internet.

How do I access Copyparty from my phone?

Make sure the phone is on the same Wi-Fi as the computer running Copyparty, then scan the QR code printed in the server's terminal with the phone's camera. The share opens in the phone's browser — no app to install. From there you can upload photos and videos from the camera roll or download files to the phone. For access away from home, put the server on your Tailscale tailnet instead of opening router ports.

Does Copyparty work on Windows?

Yes. The project ships copyparty.exe, a standalone Windows binary that needs no Python installation — double-clicking it starts a server sharing the current folder, with the same open-by-default behavior as the Python build, so create your share folder and add an account first. The Docker images also run on Windows through Docker Desktop, and WebDAV lets Windows map a Copyparty volume as an ordinary network drive.

Should I choose Copyparty or Filebrowser?

Choose Copyparty when you want a share running in under a minute with zero installation — its single-file build, QR-code phone transfers, and multi-protocol support are unmatched for quick personal sharing. Choose Filebrowser when you want a managed, Docker-first file manager with built-in user administration as the primary design. Many people end up with both: Copyparty for ad-hoc shares, Filebrowser for the permanent family server.