Littletug as an alternative to FTP uploads
With both, your clients upload large files straight to you.
A guide or an address
What your clients have to read before an FTP upload, and what they need with Littletug.
A typical FTP guide
- Install an FTP program.
- Enter the server, then the user name and password from our email. Server: ftp.your-print-shop.tld User: client-1042
- Choose port 21. If no connection comes up, switch on passive mode.
- Drag your files into the folder “upload”.
- Send us an email once the upload is done.
With Littletug
upload.your-print-shop.tld
Your client opens the link and picks their files.
You get an email when they have arrived.
What matters when receiving
An FTP login needs instructions. Your client installs a program and enters the server, user name, password and port. Anyone who does this rarely will have forgotten the steps by next time.
When it fails, the client phones you. Sometimes the firewall in their office blocks the ports FTP needs, and passive mode does not always get round it.
Then there is the server itself: updates, logins for your clients, storage. With Littletug your client gets an address on your domain and needs only a browser.
| Criterion | Littletug | FTP uploads |
|---|---|---|
| What your client needs | A browser and your link, on a phone too | An FTP program; Chrome and Firefox no longer open FTP |
| Login details | None; a password per upload link if you want one | Server, user name, password and port |
| Notice when files arrive | An email to you when a client has sent files | Only if your server can do it; otherwise the client emails you |
| Encryption | HTTPS in transit, encrypted at rest | None, not even for the password; FTPS encrypts if your server offers it |
| Company networks | Runs over HTTPS like any website | Files travel over further ports that firewalls can block; passive mode helps, but not always |
| Virus check | Yes, before download; files over 2 GB are not checked | Only if your server checks files |
| Size per file | 1 GB on Solo, up to 10 GB on Plus and Professional | No fixed limit; it depends on your server and storage |
| Broken connections | Carries on by itself while the page is open; after a reload the file starts again | Can carry on where the connection dropped, if the server and the FTP program support it |
| Upkeep | We handle it, on servers in Germany | Yours or your host’s: updates, accounts, storage |
| What Littletug does not offer |
|
|
As of 17 November 2026. Sources: RFC 2577 RFC 4217 RFC 1579 RFC 3659 Chrome 95 Firefox 90
What FTP does
FTP is an open protocol for moving files between computers. Your client connects to your server with an FTP program and puts files into a folder. Your software can pick them up from there, such as a prepress hot folder. There is no fixed size limit. A broken upload can carry on if the server and the program support it.
What Littletug does
Littletug is an upload page on your own domain, for example upload.company.tld. Your clients open the link in their browser and pick their files, with no program and no login details. You get an email when files have arrived. The files are stored on servers in Germany and stay until you delete them.
How the two differ
FTP is a tool for people who know it. Its strengths are very large files and fixed workflows. Littletug is made for clients who just want to open a link. If you need both, keep the FTP server for a few regular clients and give everyone else the upload address.
Who Littletug is for
-
Your clients send print files, and today they need an FTP guide for it.
Littletug for print shops -
You receive images from clients and agencies who have no FTP program.
Littletug for photographers -
Consultants send you drawings, and you would rather not look after a server for it.
Littletug for architects