Type Function
Library network.*
Return value Userdata
Revision Release 2023.3686
Keywords asynchronous, http, https, get, post, upload
See also network.request()


This API is a convenience method that is very similar to the asynchronous network.request(), except that always attempts to upload the request from a local file that you specify. In fact, this method simply calls network.request(), putting the source filename and baseDirectory parameters into a params.body table, adding contentType as a params.headers request header value, and specifying "upload" progress notifications.

This function returns a handle that can be passed to network.cancel() in order to cancel the request.


You cannot execute a network upload during an applicationSuspend or applicationExit event. When your application suspends, no callbacks will fire. You can work around this by saving the request you wish to make to a file upon suspension. Then, on an applicationResume event, check if there is a pending upload saved and, if so, execute it.

Network requests do not raise runtime errors in the event of failure so there is no need to wrap them in a Lua pcall() statement (errors are reported in the event sent to the network listener).


On Android, you must add the INTERNET permission to the build.settings file.

settings =
   android =
      usesPermissions =


network.upload( url, method, listener [, params], filename [, baseDirectory] [, contentType] )
url (required)

String. The HTTP request URL.

method (required)

String. The HTTP method; should typically be either "PUT" or "POST" for a file upload.

listener (required)

Listener. The listener function invoked at various phases of the HTTP operation. It is passed a networkRequest event. This API provides "upload" progress when progress is true, meaning that the listener will receive events for "began", "progress", and "ended" phases. If the progress parameter is not enabled, the listener will only be invoked with an "ended" phase.

params (optional)

Table. Table that specifies HTTP request processing options, including custom request headers. The following keys are supported:

  • headers — Table specifying header values with string keys.
  • timeout — Timeout in seconds. Default is 30 seconds. Only available on Mac/iOS.
  • bodyType — String indicating whether a string request body is "text" or "binary". Default is "text".
  • progress — Setting to true enables the progress events. Default is nil, indicating that only the "ended" phase event is desired.
filename (required)

String. The name of the file to upload.

baseDirectory (optional)

Constant. The directory of the file to upload. Defaults to system.DocumentsDirectory if not provided.

contentType (optional)

Constant. The Content-Type of the file being uploaded. While this parameter is optional, Content-Type must be provided either via this parameter or via a params.header value.


-- The following code demonstrates an HTTP post, where the request body is text from a file.
-- This example demonstrates just one possible way to upload a file. Different web servers
-- and applications support different methods of file upload. For example, some REST services
-- support upload of a binary file in the body of a PUT request. Many web servers only allow
-- file uploads using multipart/form-encoded (text) request bodies in a POST request. If you
-- are going to attempt file upload, you must first understand the specific mechanism
-- supported by the specific web server or application that you will be working with,
-- then you must form your request data and choose your request method appropriately.

local function networkListener( event )
    if ( event.isError ) then
        print( "Network error: ", event.response )
    elseif ( event.phase == "ended" ) then
        print ( "Upload complete!" )