How to download files over FTP with wget

FTP retrieval still shows up in partner exports, archive feeds, and older integrations where the remote side only gives you a file path on an FTP server. GNU wget fits that job well because it can log in from the shell, save files into a predictable directory, and resume a partial transfer without switching tools.

The main options for this workflow are --user, --ask-password, ~/.netrc, --continue, and --directory-prefix. Passive FTP is still the default, and the session transcript may show either PASV or EPSV depending on what the server offers, but both indicate that wget kept the transfer in passive mode.

Plain FTP does not encrypt the login or the file contents. Use it only on trusted network paths, keep saved credential files readable only by the account that needs them, and switch to FTPS or SFTP when the data must not travel in clear text.

Related: How to switch passive and active FTP modes in wget
Related: How to resume interrupted downloads using wget
Related: How to download files from a list with wget

Steps to download files over FTP with wget:

  1. Pull one file with a prompted password and place it under a dedicated local directory. 
    $ wget --user=svc_partner_feed_ro --ask-password --directory-prefix=partner-feed-downloads ftp://ftp.partner-feed.example.net/exports/settlement-2026-04-21.csv
Password for user 'svc_partner_feed_ro':
--2026-04-22 10:36:13--  ftp://ftp.partner-feed.example.net/exports/settlement-2026-04-21.csv
           => 'partner-feed-downloads/settlement-2026-04-21.csv'
Resolving ftp.partner-feed.example.net (ftp.partner-feed.example.net)... 198.51.100.24
Connecting to ftp.partner-feed.example.net (ftp.partner-feed.example.net)|198.51.100.24|:21... connected.
Logging in as svc_partner_feed_ro ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /exports ... done.
==> SIZE settlement-2026-04-21.csv ... 24025
==> PASV ... done.    ==> RETR settlement-2026-04-21.csv ... done.
Length: 24025 (23K) (unauthoritative)

     0K .......... .......... ...                             100% 43.1M=0.001s

2026-04-22 10:36:13 (43.1 MB/s) - 'partner-feed-downloads/settlement-2026-04-21.csv' saved [24025]

    Replace the masked host, account, and path with the real FTP target, and let the password prompt carry the secret instead of putting it on the command line.

  2. Save the FTP login in ~/.netrc when the same server is used repeatedly. 
    ~/.netrc
machine ftp.partner-feed.example.net
  login svc_partner_feed_ro
  password MASKED_PARTNER_FEED_PASSWORD
    $ chmod 600 ~/.netrc
$ ls -l ~/.netrc
-rw------- 1 user user 101 Apr 22 10:33 /home/user/.netrc

    The machine value must match the FTP hostname, and the file should stay at 600 or stricter so other local users cannot read it.

  3. Reuse the saved login for the next transfer without repeating the username or password prompt. 
    $ wget --directory-prefix=partner-feed-downloads ftp://ftp.partner-feed.example.net/exports/nightly-ledger-2026-04-21.tar.gz
--2026-04-22 10:33:25--  ftp://ftp.partner-feed.example.net/exports/nightly-ledger-2026-04-21.tar.gz
           => 'partner-feed-downloads/nightly-ledger-2026-04-21.tar.gz'
Resolving ftp.partner-feed.example.net (ftp.partner-feed.example.net)... 198.51.100.24
Connecting to ftp.partner-feed.example.net (ftp.partner-feed.example.net)|198.51.100.24|:21... connected.
Logging in as svc_partner_feed_ro ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /exports ... done.
==> SIZE nightly-ledger-2026-04-21.tar.gz ... 6291456
==> PASV ... done.    ==> RETR nightly-ledger-2026-04-21.tar.gz ... done.
Length: 6291456 (6.0M) (unauthoritative)

##### snipped #####

2026-04-22 10:33:25 (247 MB/s) - 'partner-feed-downloads/nightly-ledger-2026-04-21.tar.gz' saved [6291456]

    A clean rerun with only the FTP URL confirms that the host, login, and saved password line up before you move the job into cron or another scheduler.

  4. Resume an interrupted FTP file from the directory that already contains the partial copy. 
    $ cd partner-feed-downloads
$ wget --continue ftp://ftp.partner-feed.example.net/exports/nightly-ledger-2026-04-21.tar.gz
--2026-04-22 10:33:42--  ftp://ftp.partner-feed.example.net/exports/nightly-ledger-2026-04-21.tar.gz
           => 'nightly-ledger-2026-04-21.tar.gz'
Connecting to ftp.partner-feed.example.net (ftp.partner-feed.example.net)|198.51.100.24|:21... connected.
Logging in as svc_partner_feed_ro ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /exports ... done.
==> SIZE nightly-ledger-2026-04-21.tar.gz ... 6291456
==> PASV ... done.    ==> REST 1048576 ... done.
==> RETR nightly-ledger-2026-04-21.tar.gz ... done.
Length: 6291456 (6.0M), 5242880 (5.0M) remaining (unauthoritative)

        [ skipping 1000K ]
##### snipped #####

2026-04-22 10:33:42 (125 MB/s) - 'nightly-ledger-2026-04-21.tar.gz' saved [6291456]

    The REST line shows that the server accepted the existing local offset instead of restarting the file from byte zero. Related: How to resume interrupted downloads using wget

  5. Verify the finished files before handing them to the next job stage. 
    $ ls -lh partner-feed-downloads
total 12296
-rw-r--r-- 1 user user 6.0M Apr 22 10:33 nightly-ledger-2026-04-21.tar.gz
-rw-r--r-- 1 user user  23K Apr 22 10:36 settlement-2026-04-21.csv

    Matching the expected filenames and rough sizes is the fastest final check before an import, archive move, or downstream batch run.