Deprecate and remove support for FTP URLs.


The current FTP implementation in Google Chrome has no support for encrypted connections (FTPS), nor proxies. Usage of FTP in the browser is sufficiently low that it is no longer viable to invest in improving the existing FTP client. In addition more capable FTP clients are available on all affected platforms. Google Chrome 72+ removed support for fetching document subresources over FTP and rendering of top level FTP resources. Currently navigating to FTP URLs result in showing a directory listing or a download depending on the type of resource. A bug in Google Chrome 74+ resulted in dropping support for accessing FTP URLs over HTTP proxies. Proxy support for FTP was removed entirely in Google Chrome 76. Remaining capabilities of Google Chrome’s FTP implementation are restricted to either displaying a directory listing or downloading a resource over unencrypted connections. We would like to deprecate and remove this remaining functionality rather than maintain an insecure FTP implementation.


Status in Chromium


Removed (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.



Timeline: * M86 (2020Q4) Includes a flag for controlling overall FTP support. FTP is enabled by default, but turned down via an experiment for pre-release channels and 1% of Stable channel users. FTP can be re-enabled via --enable-ftp command line flag or equivalently by enabling the FtpProtocol feature via "--enable-features=FtpProtocol" * M87 FTP support is disabled by default but enabled for 50% of stable channel users via server configuration. Flags for re-enabling FTP support is still present as with M86. * M88 FTP support is disabled by default for all users. Flags for re-enabling FTP support is still present as with M86. * M95 FTP support removed from codebase. (Updated: Previously code removal was slated for M88. It is now targetting M95)

Search tags

ftp, deprecate,

Last updated on 2021-12-05