Guides

What do you want to do with pipeit?

Send files, connect a new device, set up a server as a receiver or connect an AI assistant: here are the steps, and help when a connection does not work.

Start here

Send files
Between any two of your devices, in a few steps.
Save on your iPhone
In the app or from the browser.
Connect devices
Add a device you own.
Set up a server
A Linux receiver that stays on.
Check the connection
See which route is used.
Connect an AI assistant
ChatGPT, Codex, Claude, Gemini, Grok.

Everyday sending

Send files between your devices, save them on your phone and share with people you know.

Apps and browser
Send files between two of your devices
Pick files, choose the receiving device, check the connection and wait for “Received and verified”.
Apps and browser
Save on iPhone and iPad from the browser
Accept the transfer, save the file through the share menu and keep its original file name.
Apps and browser
Send large files
In the browser, large transfers use the encrypted pipeit relay and need both sides reachable until they finish; the apps also connect directly.
Apps and browser
Send a folder in the browser
Choose a folder, keep empty subfolders where the browser allows it and send it as a protected archive.
Apps and browser
Invite a contact and send to another person
Invite someone, let them accept and send to a destination you both share.

Devices and account

Apps and browser
Sign in and stay signed in
Sign in with an email code, stay signed in on your own device and confirm sensitive actions without starting over.
Apps and browser
Connect a device of your own
Add a new browser or device to your account and check its identity before you approve it.
Apps and browser
Work with shared destinations
Pick your workspace, check your role and send to the destination that was released for you.
Apps and browser
Regain device access after a loss
Rebuild device access when no paired device is left, and understand what that replaces.
Apps and browser
Manage sign-in methods, sessions and access
Link another sign-in method, revoke access you no longer need and know what deleting an account means.

Servers and command line

Set up a receiver, name destinations and send from a terminal.

Command line and servers
Sign in with the CLI, even without a browser on the server
Start the sign-in on a server and approve it on your computer or phone.
Command line and servers
Set up Linux as a permanent receiver
Let a server accept files from one named sender into a private inbox.
Command line and servers
Receiver B: create a named destination
Give a private folder on the receiver a short alias that senders can pick.
Command line and servers
Sender A: choose the destination and send a file
Pick the receiver’s alias and send a large file with a receipt you can rely on.
Command line and servers
Send several files as one transfer
Use a group transfer when you want one acceptance for many files, and resume it with the same ID.
Command line and servers
Status, progress and resuming
Read the state of a transfer and continue the same job instead of starting a new one.
Command line and servers
Offline between servers: local pairing on the command line
Pair two servers or computers with a local identity on the command line so they can exchange files across a network that has no internet.

Folders and automation

Send whole folders, deliver a website and fit pipeit into CI.

Command line and servers
Send a folder or only its contents
Send a whole folder with or without its outer folder, including dotfiles and empty subfolders.
Command line and servers
Does a folder have to be stored twice first?
The native folder stream builds no full archive, but the receiving side still needs space while it checks.
Command line and servers
Store, update or activate a folder
Three receiving modes with different effects, and what none of them does.
Command line and servers
Example: deliver the contents of a website
Send a build as a prepared state and switch to it deliberately afterwards.
Command line and servers
Remove old files you no longer need
Normal sending never deletes anything. For a managed set of files there are three separate, deliberate actions.
Command line and servers
A CI step with a verifiable result
Deliver a folder from a pipeline and let the exit code decide whether the next step may run.

Connection and troubleshooting

Understand direct and server routes, check them and fix problems.

Apps and browser
Check the connection and look back at it later
See which route is checked before sending and which one was actually used afterwards.
Command line and servers
Check the direct route and set the fallback
Probe a direct route, choose a route per transfer and control the account-wide fallback.
Command line and servers
Speed test and support report
Run a deliberate, limited measurement and keep the support ID for a conversation with us.
Direct, server route and routed networks: which way works?
What “direct” really means, when pipeit routes through its servers and what you can check.
Solve transfer problems
Check the specific problem instead of starting over: a quick decision list and the common symptoms with their next step.

AI and developers

Connect Claude, ChatGPT, Gemini, Grok, Cursor and Microsoft 365 Copilot, build on the API and read the security questions.

Security and frequently asked questions
What pipeit protects, where files are stored, what a receipt confirms and where the limits are.
Build on pipeit: your own clients and the API
One shared contract for all clients, and a sensible order for building your own.
Connect ChatGPT, Codex, Claude, Gemini and Grok
Add pipeit as a remote connector, sign in with your pipeit account and choose which devices the assistant may use.

Want to know how it works?

Architecture, encryption, connections and recovery, explained for the technically curious.

Under the hood