Flying Pigs — Progress Display

Understanding the Flying Pigs progress display

While a run is going, Flying Pigs shows what it is doing: which photos are being processed in your browser, what is waiting to upload, what each upload lane is sending, and how far the run has got. When the run ends, a summary card says what landed.

You do not need to watch any of it. It is there so you can see the run is still working during big uploads, slow server answers, short network drops and automatic retries.

The run buttons

• Start upload starts the run. Pressing it again while a run is going adds the newly staged files to the same run.
• Pause stops sending new work. Uploads already on the wire finish first.
• Resume carries on from where the run paused.
• Stop ends the run. Uploads already on the wire are allowed to finish, so Start reads Wait… for a few seconds.

The run options and settings are locked while a run is going, so every file in the run gets the same settings.

Upload progress card

The card appears over the settings when a run starts. Right after you press Start it names the step it is on, such as Checking the image engine…, until the run gets under way.

Upload count and timer

The line under the bars shows how many entries are finished out of the whole run, with the run time beside it:

Uploaded 403 of 2,790 entries    00:01:27

An entry is one media library item: the photo with all of its sizes. The long bar above the line fills as entries finish.

The timer keeps running even when the count stops for a moment. That happens while the browser works on a big photo, while the server files a batch, or while a failed request waits to be sent again.

Process and Queue graph

The small graph shows the last 50 seconds:

• Process (blue) is how many photos your browser is processing at that moment.
• Queue (orange) is how much finished work is waiting to upload.

Hover over the graph to see the exact values at any second, including the queue in MB and entries.

The two lines tell you what sets the pace. A high queue means the upload is the slow side: your connection or the host. A queue near zero with Process busy means the browser is the slow side, and the uploads are waiting for it. Both are normal.

Upload lane bars

Each short bar is one upload lane, with the size of the batch it is sending, for example ↑12.4 MB. Six lanes show as two rows of three.

• A bar fills as its batch is sent.
• A full bar with moving stripes has sent its batch and is waiting for the server to file the entries.
• A finished bar fades out, and a new batch takes the lane.

Free uploads on one lane. Pro's turbo boost uses up to six, and drops to two when the server slows down or pushes back.

Throttling and pauses

If you set a limit in the Advanced panel, the card says so while it holds the run back, for example Holding to stay under 2 MB/s…. The run is slow on purpose, because of the limit you set.

If Pause uploads is on, the bars turn amber during each scheduled pause, then carry on.

Pop out

The Pop out button in the card's title opens the card in a small always-on-top window, and it can open by itself when a run starts. The run keeps full speed while you work in other windows. Keep the uploader tab open. The window closes itself when the upload finishes.

It works in Chrome, Edge, Brave and Firefox.

The file list

Every file in the run has a row with its thumbnail, a status and a detail line:

• Pending covers the steps before it lands: queued, processing in the browser, batched, uploading.
• Done means the entry is in the media library. Click the thumbnail or the name to open it.
• Replaced means an existing entry was overwritten in place (Pro).
• Retrying means a request failed and is being sent again.
• Failed means this file could not be uploaded. The detail line says why.
• Stopped means the run was stopped before this file was sent.

Use the search box and the status filter above the list to find a file in a big run.

Network errors

The Network errors button appears beside the run buttons once a request fails. It shows failed requests over all requests sent in this run, for example 3 / 412, and starts again at zero on each run. Click it to see each error with its time.

These are connection problems: a timeout, a dropped connection, a proxy or Cloudflare error, or a busy server answering 503 or 429. Flying Pigs sends every failed request again. The count is there so you can see the retries happening. Nothing has been lost.

A run stops only when requests keep failing for the whole Upload timeout in the Advanced panel, 370 seconds by default, without a single successful upload. The summary card is then titled Upload Network Error. Check your connection and that the site is up, then start the run again.

Upload issues

The Upload issues button shows failed files over all files in the list. Click it for each file with its message. Click a file name to find it in the list.

Upload issues belong to one file. They do not stop the run, and the rest of the files carry on. Typical causes are a file the browser could not read as an image, a file type WordPress does not allow, or an overwrite that could not be matched safely.

Network errors and upload issues are different

• Network errors are about the connection. Flying Pigs retries them and the files still land.
• Upload issues are about one file. That file did not land, and the message says why.

The summary card

When the run ends, the card is titled Upload complete, Upload stopped or Upload Network Error. It shows:

• How many entries were added or replaced, and how long it took, with any failures and recovered network errors.
• Optimizer Results – Average Savings: how much smaller the base image, the WebP and AVIF copies and their thumbnails came out than the source. n/a means nothing of that kind was made.
• Browser processing: entries per second, the time per entry, how many workers ran, and how much of the run had uploads in flight. A low in-flight share means the browser set the pace, not the connection.
• Which protocol carried the uploads, for example Sent over HTTP/3.
• With Pro's WooCommerce option: how many photos were attached to how many products by SKU, and how many had no matching product.
• Any WebP or AVIF copies thrown away because they came out larger than the source. That is normal: some images do not compress better as WebP or AVIF.

The card stays on the page until you close it or start another run.

When a run looks stuck

If the count stops but the timer, the graph or the lane bars are still moving, the run is working. It may be:

• processing a big photo in the browser
• waiting for the server to file a batch (striped bar)
• resending a request after a network error
• holding to a limit you set, or taking a scheduled pause

Let it carry on. Flying Pigs recovers from short network and server drops by itself.

What you normally need to do

Usually nothing. If the run is moving, let it finish.

If network errors keep climbing for several minutes, check your connection and the site. If a file shows under Upload issues, read its message when the run ends. It affects only that file.