What is the difference between curl and wget?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
185
down vote

favorite
58












I am keen to know the difference between curl and wget. Both are used to get files and documents but what the key difference between them.



Why are there two different programs?










share|improve this question



















  • 3




    Main difference is that wget is used to download things while curl is used to test communication by using a specific protocol.
    – Pithikos
    Aug 15 '14 at 13:29






  • 3




    An interesting fact about wget: > Wget can be typed in using only the left hand on a qwerty keyboard!
    – Habeeb Perwad
    Sep 26 '15 at 9:50










  • From curl author: daniel.haxx.se/docs/curl-vs-wget.html
    – Vanni
    Oct 16 '17 at 13:29














up vote
185
down vote

favorite
58












I am keen to know the difference between curl and wget. Both are used to get files and documents but what the key difference between them.



Why are there two different programs?










share|improve this question



















  • 3




    Main difference is that wget is used to download things while curl is used to test communication by using a specific protocol.
    – Pithikos
    Aug 15 '14 at 13:29






  • 3




    An interesting fact about wget: > Wget can be typed in using only the left hand on a qwerty keyboard!
    – Habeeb Perwad
    Sep 26 '15 at 9:50










  • From curl author: daniel.haxx.se/docs/curl-vs-wget.html
    – Vanni
    Oct 16 '17 at 13:29












up vote
185
down vote

favorite
58









up vote
185
down vote

favorite
58






58





I am keen to know the difference between curl and wget. Both are used to get files and documents but what the key difference between them.



Why are there two different programs?










share|improve this question















I am keen to know the difference between curl and wget. Both are used to get files and documents but what the key difference between them.



Why are there two different programs?







utilities wget curl download






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 31 '14 at 16:42









polym

6,33643155




6,33643155










asked Sep 7 '12 at 4:51









lakesh

1,2563119




1,2563119







  • 3




    Main difference is that wget is used to download things while curl is used to test communication by using a specific protocol.
    – Pithikos
    Aug 15 '14 at 13:29






  • 3




    An interesting fact about wget: > Wget can be typed in using only the left hand on a qwerty keyboard!
    – Habeeb Perwad
    Sep 26 '15 at 9:50










  • From curl author: daniel.haxx.se/docs/curl-vs-wget.html
    – Vanni
    Oct 16 '17 at 13:29












  • 3




    Main difference is that wget is used to download things while curl is used to test communication by using a specific protocol.
    – Pithikos
    Aug 15 '14 at 13:29






  • 3




    An interesting fact about wget: > Wget can be typed in using only the left hand on a qwerty keyboard!
    – Habeeb Perwad
    Sep 26 '15 at 9:50










  • From curl author: daniel.haxx.se/docs/curl-vs-wget.html
    – Vanni
    Oct 16 '17 at 13:29







3




3




Main difference is that wget is used to download things while curl is used to test communication by using a specific protocol.
– Pithikos
Aug 15 '14 at 13:29




Main difference is that wget is used to download things while curl is used to test communication by using a specific protocol.
– Pithikos
Aug 15 '14 at 13:29




3




3




An interesting fact about wget: > Wget can be typed in using only the left hand on a qwerty keyboard!
– Habeeb Perwad
Sep 26 '15 at 9:50




An interesting fact about wget: > Wget can be typed in using only the left hand on a qwerty keyboard!
– Habeeb Perwad
Sep 26 '15 at 9:50












From curl author: daniel.haxx.se/docs/curl-vs-wget.html
– Vanni
Oct 16 '17 at 13:29




From curl author: daniel.haxx.se/docs/curl-vs-wget.html
– Vanni
Oct 16 '17 at 13:29










3 Answers
3






active

oldest

votes

















up vote
184
down vote



accepted










The main differences are:




  • wget's major strong side compared to curl is its ability to download recursively.


  • wget is command line only. There's no lib or anything, but curl's features are powered by libcurl.


  • curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP. wget supports HTTP, HTTPS and FTP.


  • curl builds and runs on more platforms than wget.


  • wget it's released under a free software copyleft license (the GNU GPL). curl is released under a free software permissive license (a MIT derivate).


  • curl offers upload and sending capabilities. wget only offers plain HTTP POST support.

You can see more details at the following link:



curl vs Wget






share|improve this answer






















  • Thanks, this is exactly what I've been wondering about for a few hours. I used wget to do a recursive spider on a site, seems stalled on a page that has eleventy bazillion links on it. The reality is it's running at 100% CPU on one core. Was hoping that there was something better that does that newfangled multicore thing I've been hearing about.
    – Brian Topping
    Jun 7 '15 at 10:13






  • 1




    One of the things wget does that is left out of this answer is http mirroring (or 'spidering') ability. curl is very good at what it does, but it alone is not intended to be used to mirror a web site.
    – jsbillings
    Sep 26 '15 at 12:38










  • What about wput being an alias, supporting ftp.
    – mckenzm
    Jan 23 '17 at 5:01










  • These phrases have no sense: "and all copyrights are assigned to FSF", "is entirely stand-alone and independent with no organization parenting at all". It's obvious that the author of cURL is the copyright owner of it. It's obvious that the author of wget is the copyright owner of it. But both are free as in freedom software. You can say instead that wget is under a copyleft license, and cURL under a permissive license.
    – Valerio Bozz
    Apr 11 at 11:59

















up vote
33
down vote













In a few words:




  • wget is a tool to download files from servers


  • curl is a tool that let's you exchange requests/responses with a server

wget



Wget solely let's you download files from an HTTP/HTTPS or FTP server. You give it a link and it automatically downloads the file where the link points to. It builds the request automatically.



curl



Curl in contrast to wget let's you build the request as you wish. This gives a lot of freedom to the user and makes an amazing debugging tool. Add to that the other key difference between the two; the plethora of protocols supported. Curl supports FTP, FTPS, Gopher, HTTP, HTTPS, SCP, SFTP, TFTP, Telnet, DICT, LDAP, LDAPS, IMAP, POP3, SMTP, RTSP and URI. Combine these two key points and you have an amazing tool to test protocols, test server configuration, etc.



As many say, you can download a file with curl. That however is only useful if you happen to want to downlaod a file from a server that uses a protocol that wget doesn't support.






share|improve this answer


















  • 2




    Actually wget also follows the redirect then saves the response unlike curl. Both can achieve the opposite to the default behaviour wget -qO - http://google.co.uk/ or curl http://google.co.uk/ > index.html
    – Matt
    Aug 15 '14 at 17:46










  • @mtm curl http://google.co.uk/ > index.html is not using an inbuilt functionality though. Anyway the main distinction is the purpose each tool was made for. There is not denying that tools evolve and many times deviate from their initial trajectory.
    – Pithikos
    Aug 16 '14 at 10:24










  • @mtm curl http://google.co.uk -o index.html would use curl's internals instead of shell output redirection with >.
    – Petrus Repo
    Jan 15 '15 at 11:35

















up vote
13
down vote













Actually, the major difference is that curl includes a library (libcurl), and that library is widely used by other applications. wget is standalone.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f47434%2fwhat-is-the-difference-between-curl-and-wget%23new-answer', 'question_page');

    );

    Post as a guest






























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    184
    down vote



    accepted










    The main differences are:




    • wget's major strong side compared to curl is its ability to download recursively.


    • wget is command line only. There's no lib or anything, but curl's features are powered by libcurl.


    • curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP. wget supports HTTP, HTTPS and FTP.


    • curl builds and runs on more platforms than wget.


    • wget it's released under a free software copyleft license (the GNU GPL). curl is released under a free software permissive license (a MIT derivate).


    • curl offers upload and sending capabilities. wget only offers plain HTTP POST support.

    You can see more details at the following link:



    curl vs Wget






    share|improve this answer






















    • Thanks, this is exactly what I've been wondering about for a few hours. I used wget to do a recursive spider on a site, seems stalled on a page that has eleventy bazillion links on it. The reality is it's running at 100% CPU on one core. Was hoping that there was something better that does that newfangled multicore thing I've been hearing about.
      – Brian Topping
      Jun 7 '15 at 10:13






    • 1




      One of the things wget does that is left out of this answer is http mirroring (or 'spidering') ability. curl is very good at what it does, but it alone is not intended to be used to mirror a web site.
      – jsbillings
      Sep 26 '15 at 12:38










    • What about wput being an alias, supporting ftp.
      – mckenzm
      Jan 23 '17 at 5:01










    • These phrases have no sense: "and all copyrights are assigned to FSF", "is entirely stand-alone and independent with no organization parenting at all". It's obvious that the author of cURL is the copyright owner of it. It's obvious that the author of wget is the copyright owner of it. But both are free as in freedom software. You can say instead that wget is under a copyleft license, and cURL under a permissive license.
      – Valerio Bozz
      Apr 11 at 11:59














    up vote
    184
    down vote



    accepted










    The main differences are:




    • wget's major strong side compared to curl is its ability to download recursively.


    • wget is command line only. There's no lib or anything, but curl's features are powered by libcurl.


    • curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP. wget supports HTTP, HTTPS and FTP.


    • curl builds and runs on more platforms than wget.


    • wget it's released under a free software copyleft license (the GNU GPL). curl is released under a free software permissive license (a MIT derivate).


    • curl offers upload and sending capabilities. wget only offers plain HTTP POST support.

    You can see more details at the following link:



    curl vs Wget






    share|improve this answer






















    • Thanks, this is exactly what I've been wondering about for a few hours. I used wget to do a recursive spider on a site, seems stalled on a page that has eleventy bazillion links on it. The reality is it's running at 100% CPU on one core. Was hoping that there was something better that does that newfangled multicore thing I've been hearing about.
      – Brian Topping
      Jun 7 '15 at 10:13






    • 1




      One of the things wget does that is left out of this answer is http mirroring (or 'spidering') ability. curl is very good at what it does, but it alone is not intended to be used to mirror a web site.
      – jsbillings
      Sep 26 '15 at 12:38










    • What about wput being an alias, supporting ftp.
      – mckenzm
      Jan 23 '17 at 5:01










    • These phrases have no sense: "and all copyrights are assigned to FSF", "is entirely stand-alone and independent with no organization parenting at all". It's obvious that the author of cURL is the copyright owner of it. It's obvious that the author of wget is the copyright owner of it. But both are free as in freedom software. You can say instead that wget is under a copyleft license, and cURL under a permissive license.
      – Valerio Bozz
      Apr 11 at 11:59












    up vote
    184
    down vote



    accepted







    up vote
    184
    down vote



    accepted






    The main differences are:




    • wget's major strong side compared to curl is its ability to download recursively.


    • wget is command line only. There's no lib or anything, but curl's features are powered by libcurl.


    • curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP. wget supports HTTP, HTTPS and FTP.


    • curl builds and runs on more platforms than wget.


    • wget it's released under a free software copyleft license (the GNU GPL). curl is released under a free software permissive license (a MIT derivate).


    • curl offers upload and sending capabilities. wget only offers plain HTTP POST support.

    You can see more details at the following link:



    curl vs Wget






    share|improve this answer














    The main differences are:




    • wget's major strong side compared to curl is its ability to download recursively.


    • wget is command line only. There's no lib or anything, but curl's features are powered by libcurl.


    • curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP. wget supports HTTP, HTTPS and FTP.


    • curl builds and runs on more platforms than wget.


    • wget it's released under a free software copyleft license (the GNU GPL). curl is released under a free software permissive license (a MIT derivate).


    • curl offers upload and sending capabilities. wget only offers plain HTTP POST support.

    You can see more details at the following link:



    curl vs Wget







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Aug 31 at 6:16









    Pradeep Anchan

    53




    53










    answered Sep 7 '12 at 4:56









    Saeed Zarinfam

    2,34221214




    2,34221214











    • Thanks, this is exactly what I've been wondering about for a few hours. I used wget to do a recursive spider on a site, seems stalled on a page that has eleventy bazillion links on it. The reality is it's running at 100% CPU on one core. Was hoping that there was something better that does that newfangled multicore thing I've been hearing about.
      – Brian Topping
      Jun 7 '15 at 10:13






    • 1




      One of the things wget does that is left out of this answer is http mirroring (or 'spidering') ability. curl is very good at what it does, but it alone is not intended to be used to mirror a web site.
      – jsbillings
      Sep 26 '15 at 12:38










    • What about wput being an alias, supporting ftp.
      – mckenzm
      Jan 23 '17 at 5:01










    • These phrases have no sense: "and all copyrights are assigned to FSF", "is entirely stand-alone and independent with no organization parenting at all". It's obvious that the author of cURL is the copyright owner of it. It's obvious that the author of wget is the copyright owner of it. But both are free as in freedom software. You can say instead that wget is under a copyleft license, and cURL under a permissive license.
      – Valerio Bozz
      Apr 11 at 11:59
















    • Thanks, this is exactly what I've been wondering about for a few hours. I used wget to do a recursive spider on a site, seems stalled on a page that has eleventy bazillion links on it. The reality is it's running at 100% CPU on one core. Was hoping that there was something better that does that newfangled multicore thing I've been hearing about.
      – Brian Topping
      Jun 7 '15 at 10:13






    • 1




      One of the things wget does that is left out of this answer is http mirroring (or 'spidering') ability. curl is very good at what it does, but it alone is not intended to be used to mirror a web site.
      – jsbillings
      Sep 26 '15 at 12:38










    • What about wput being an alias, supporting ftp.
      – mckenzm
      Jan 23 '17 at 5:01










    • These phrases have no sense: "and all copyrights are assigned to FSF", "is entirely stand-alone and independent with no organization parenting at all". It's obvious that the author of cURL is the copyright owner of it. It's obvious that the author of wget is the copyright owner of it. But both are free as in freedom software. You can say instead that wget is under a copyleft license, and cURL under a permissive license.
      – Valerio Bozz
      Apr 11 at 11:59















    Thanks, this is exactly what I've been wondering about for a few hours. I used wget to do a recursive spider on a site, seems stalled on a page that has eleventy bazillion links on it. The reality is it's running at 100% CPU on one core. Was hoping that there was something better that does that newfangled multicore thing I've been hearing about.
    – Brian Topping
    Jun 7 '15 at 10:13




    Thanks, this is exactly what I've been wondering about for a few hours. I used wget to do a recursive spider on a site, seems stalled on a page that has eleventy bazillion links on it. The reality is it's running at 100% CPU on one core. Was hoping that there was something better that does that newfangled multicore thing I've been hearing about.
    – Brian Topping
    Jun 7 '15 at 10:13




    1




    1




    One of the things wget does that is left out of this answer is http mirroring (or 'spidering') ability. curl is very good at what it does, but it alone is not intended to be used to mirror a web site.
    – jsbillings
    Sep 26 '15 at 12:38




    One of the things wget does that is left out of this answer is http mirroring (or 'spidering') ability. curl is very good at what it does, but it alone is not intended to be used to mirror a web site.
    – jsbillings
    Sep 26 '15 at 12:38












    What about wput being an alias, supporting ftp.
    – mckenzm
    Jan 23 '17 at 5:01




    What about wput being an alias, supporting ftp.
    – mckenzm
    Jan 23 '17 at 5:01












    These phrases have no sense: "and all copyrights are assigned to FSF", "is entirely stand-alone and independent with no organization parenting at all". It's obvious that the author of cURL is the copyright owner of it. It's obvious that the author of wget is the copyright owner of it. But both are free as in freedom software. You can say instead that wget is under a copyleft license, and cURL under a permissive license.
    – Valerio Bozz
    Apr 11 at 11:59




    These phrases have no sense: "and all copyrights are assigned to FSF", "is entirely stand-alone and independent with no organization parenting at all". It's obvious that the author of cURL is the copyright owner of it. It's obvious that the author of wget is the copyright owner of it. But both are free as in freedom software. You can say instead that wget is under a copyleft license, and cURL under a permissive license.
    – Valerio Bozz
    Apr 11 at 11:59












    up vote
    33
    down vote













    In a few words:




    • wget is a tool to download files from servers


    • curl is a tool that let's you exchange requests/responses with a server

    wget



    Wget solely let's you download files from an HTTP/HTTPS or FTP server. You give it a link and it automatically downloads the file where the link points to. It builds the request automatically.



    curl



    Curl in contrast to wget let's you build the request as you wish. This gives a lot of freedom to the user and makes an amazing debugging tool. Add to that the other key difference between the two; the plethora of protocols supported. Curl supports FTP, FTPS, Gopher, HTTP, HTTPS, SCP, SFTP, TFTP, Telnet, DICT, LDAP, LDAPS, IMAP, POP3, SMTP, RTSP and URI. Combine these two key points and you have an amazing tool to test protocols, test server configuration, etc.



    As many say, you can download a file with curl. That however is only useful if you happen to want to downlaod a file from a server that uses a protocol that wget doesn't support.






    share|improve this answer


















    • 2




      Actually wget also follows the redirect then saves the response unlike curl. Both can achieve the opposite to the default behaviour wget -qO - http://google.co.uk/ or curl http://google.co.uk/ > index.html
      – Matt
      Aug 15 '14 at 17:46










    • @mtm curl http://google.co.uk/ > index.html is not using an inbuilt functionality though. Anyway the main distinction is the purpose each tool was made for. There is not denying that tools evolve and many times deviate from their initial trajectory.
      – Pithikos
      Aug 16 '14 at 10:24










    • @mtm curl http://google.co.uk -o index.html would use curl's internals instead of shell output redirection with >.
      – Petrus Repo
      Jan 15 '15 at 11:35














    up vote
    33
    down vote













    In a few words:




    • wget is a tool to download files from servers


    • curl is a tool that let's you exchange requests/responses with a server

    wget



    Wget solely let's you download files from an HTTP/HTTPS or FTP server. You give it a link and it automatically downloads the file where the link points to. It builds the request automatically.



    curl



    Curl in contrast to wget let's you build the request as you wish. This gives a lot of freedom to the user and makes an amazing debugging tool. Add to that the other key difference between the two; the plethora of protocols supported. Curl supports FTP, FTPS, Gopher, HTTP, HTTPS, SCP, SFTP, TFTP, Telnet, DICT, LDAP, LDAPS, IMAP, POP3, SMTP, RTSP and URI. Combine these two key points and you have an amazing tool to test protocols, test server configuration, etc.



    As many say, you can download a file with curl. That however is only useful if you happen to want to downlaod a file from a server that uses a protocol that wget doesn't support.






    share|improve this answer


















    • 2




      Actually wget also follows the redirect then saves the response unlike curl. Both can achieve the opposite to the default behaviour wget -qO - http://google.co.uk/ or curl http://google.co.uk/ > index.html
      – Matt
      Aug 15 '14 at 17:46










    • @mtm curl http://google.co.uk/ > index.html is not using an inbuilt functionality though. Anyway the main distinction is the purpose each tool was made for. There is not denying that tools evolve and many times deviate from their initial trajectory.
      – Pithikos
      Aug 16 '14 at 10:24










    • @mtm curl http://google.co.uk -o index.html would use curl's internals instead of shell output redirection with >.
      – Petrus Repo
      Jan 15 '15 at 11:35












    up vote
    33
    down vote










    up vote
    33
    down vote









    In a few words:




    • wget is a tool to download files from servers


    • curl is a tool that let's you exchange requests/responses with a server

    wget



    Wget solely let's you download files from an HTTP/HTTPS or FTP server. You give it a link and it automatically downloads the file where the link points to. It builds the request automatically.



    curl



    Curl in contrast to wget let's you build the request as you wish. This gives a lot of freedom to the user and makes an amazing debugging tool. Add to that the other key difference between the two; the plethora of protocols supported. Curl supports FTP, FTPS, Gopher, HTTP, HTTPS, SCP, SFTP, TFTP, Telnet, DICT, LDAP, LDAPS, IMAP, POP3, SMTP, RTSP and URI. Combine these two key points and you have an amazing tool to test protocols, test server configuration, etc.



    As many say, you can download a file with curl. That however is only useful if you happen to want to downlaod a file from a server that uses a protocol that wget doesn't support.






    share|improve this answer














    In a few words:




    • wget is a tool to download files from servers


    • curl is a tool that let's you exchange requests/responses with a server

    wget



    Wget solely let's you download files from an HTTP/HTTPS or FTP server. You give it a link and it automatically downloads the file where the link points to. It builds the request automatically.



    curl



    Curl in contrast to wget let's you build the request as you wish. This gives a lot of freedom to the user and makes an amazing debugging tool. Add to that the other key difference between the two; the plethora of protocols supported. Curl supports FTP, FTPS, Gopher, HTTP, HTTPS, SCP, SFTP, TFTP, Telnet, DICT, LDAP, LDAPS, IMAP, POP3, SMTP, RTSP and URI. Combine these two key points and you have an amazing tool to test protocols, test server configuration, etc.



    As many say, you can download a file with curl. That however is only useful if you happen to want to downlaod a file from a server that uses a protocol that wget doesn't support.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Jan 15 '15 at 14:27

























    answered Aug 15 '14 at 13:13









    Pithikos

    1,09931318




    1,09931318







    • 2




      Actually wget also follows the redirect then saves the response unlike curl. Both can achieve the opposite to the default behaviour wget -qO - http://google.co.uk/ or curl http://google.co.uk/ > index.html
      – Matt
      Aug 15 '14 at 17:46










    • @mtm curl http://google.co.uk/ > index.html is not using an inbuilt functionality though. Anyway the main distinction is the purpose each tool was made for. There is not denying that tools evolve and many times deviate from their initial trajectory.
      – Pithikos
      Aug 16 '14 at 10:24










    • @mtm curl http://google.co.uk -o index.html would use curl's internals instead of shell output redirection with >.
      – Petrus Repo
      Jan 15 '15 at 11:35












    • 2




      Actually wget also follows the redirect then saves the response unlike curl. Both can achieve the opposite to the default behaviour wget -qO - http://google.co.uk/ or curl http://google.co.uk/ > index.html
      – Matt
      Aug 15 '14 at 17:46










    • @mtm curl http://google.co.uk/ > index.html is not using an inbuilt functionality though. Anyway the main distinction is the purpose each tool was made for. There is not denying that tools evolve and many times deviate from their initial trajectory.
      – Pithikos
      Aug 16 '14 at 10:24










    • @mtm curl http://google.co.uk -o index.html would use curl's internals instead of shell output redirection with >.
      – Petrus Repo
      Jan 15 '15 at 11:35







    2




    2




    Actually wget also follows the redirect then saves the response unlike curl. Both can achieve the opposite to the default behaviour wget -qO - http://google.co.uk/ or curl http://google.co.uk/ > index.html
    – Matt
    Aug 15 '14 at 17:46




    Actually wget also follows the redirect then saves the response unlike curl. Both can achieve the opposite to the default behaviour wget -qO - http://google.co.uk/ or curl http://google.co.uk/ > index.html
    – Matt
    Aug 15 '14 at 17:46












    @mtm curl http://google.co.uk/ > index.html is not using an inbuilt functionality though. Anyway the main distinction is the purpose each tool was made for. There is not denying that tools evolve and many times deviate from their initial trajectory.
    – Pithikos
    Aug 16 '14 at 10:24




    @mtm curl http://google.co.uk/ > index.html is not using an inbuilt functionality though. Anyway the main distinction is the purpose each tool was made for. There is not denying that tools evolve and many times deviate from their initial trajectory.
    – Pithikos
    Aug 16 '14 at 10:24












    @mtm curl http://google.co.uk -o index.html would use curl's internals instead of shell output redirection with >.
    – Petrus Repo
    Jan 15 '15 at 11:35




    @mtm curl http://google.co.uk -o index.html would use curl's internals instead of shell output redirection with >.
    – Petrus Repo
    Jan 15 '15 at 11:35










    up vote
    13
    down vote













    Actually, the major difference is that curl includes a library (libcurl), and that library is widely used by other applications. wget is standalone.






    share|improve this answer
























      up vote
      13
      down vote













      Actually, the major difference is that curl includes a library (libcurl), and that library is widely used by other applications. wget is standalone.






      share|improve this answer






















        up vote
        13
        down vote










        up vote
        13
        down vote









        Actually, the major difference is that curl includes a library (libcurl), and that library is widely used by other applications. wget is standalone.






        share|improve this answer












        Actually, the major difference is that curl includes a library (libcurl), and that library is widely used by other applications. wget is standalone.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 20 '13 at 17:02









        sendmoreinfo

        1,7191030




        1,7191030



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f47434%2fwhat-is-the-difference-between-curl-and-wget%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay