Osenpa
Just Converter guide

Resume or Retry a File Conversion on Windows

Read per-file results, retry failed inputs and continue an interrupted conversion without accidentally rerunning completed files.

By Osenpa · Updated · Reviewed
On this page

Short answer

Open Results and check which files succeeded, failed, were skipped or were canceled. Correct the reported problem before retrying. Retry failed files only selects failed and canceled inputs when that button is available; Retry with same settings reruns the original job, including completed files.

Before you start

  • Just Converter on Windows and a completed or interrupted job in Results.
  • The original input files and access to the output folder.
  • For practice, three copied images and a separate empty output folder.

Start here

  1. Use a small practice batch

    Add three copied images, choose JPG and a separate output folder, then review preflight and run the job. If all three succeed, open the outputs and stop: no retry is needed. Use the following steps when a real job reports a problem; do not damage files to manufacture a failure.

  2. Read Results file by file

    Match each input name with its status and reported output. Use Open output for a successful result and inspect the file. A partly successful job can contain usable outputs alongside failures; its overall status is not a reason to rerun every input.

  3. Correct the reported cause

    For a permission error, choose a writable destination. For a missing engine or unsupported operation, resolve that requirement and recheck compatibility. Use Edit settings when the selected conversion settings need to change. Keep successful outputs available while you investigate.

  4. Retry only eligible files when offered

    Choose Retry failed files only when the button appears and the saved settings are still appropriate. It immediately starts a new run for failed and canceled inputs from the last result, excluding successful and skipped inputs; it does not reopen preflight. The button is offered when at least one file failed, so it may be absent for a canceled-only job.

  5. Continue a canceled-only or changed job

    If the failed-only button is absent, or the conversion settings must change, start a new job containing only the unfinished inputs. Review their destination, output names and collision behavior before running. This repeats conversion for those inputs; it does not continue from a partially encoded frame or byte.

  6. Verify the new outputs

    Check the new per-file results and open each important output in its receiving application. Compare the completed set with the original input list so a skipped or still-failed file is not mistaken for a finished one.

Check your result

  • Every original input is accounted for as completed or still requiring action.
  • Previously successful outputs remain available and open correctly.
  • The reported failure cause was corrected before retrying.
  • The chosen collision rule handles existing output names as intended.
When Retry with same settings is appropriate

Retry with same settings restarts the original job snapshot, including inputs that already succeeded. Use it only when the entire job should run again.

Review collisions first. Rename creates another name, Overwrite replaces an existing destination through the app's staged process, and Skip can leave outputs unprocessed. Source files are not overwrite targets.

Failed, canceled and skipped are different

Failed means the file reported an error. Canceled means conversion was interrupted. Retry failed files only includes these two statuses when it is available.

Skipped files are excluded from failed-only retry. Inspect the reason, such as an existing destination under Skip, and decide whether that file needs a new job.

Retry settings and output quality

Retry failed files only uses the last job's saved settings. After choosing Edit settings, review the current file list and run the revised job; do not assume the old retry command adopts unsaved changes.

A successful conversion status means the operation completed. It does not guarantee that layout, image detail, audio tracks or formula values match what the receiving system needs.

If the same error returns

Read the per-file message, check that the input still exists and confirm output permissions and optional components. Repeatedly retrying an unchanged failure is unlikely to help.

Copy diagnostic information provides redacted support details. The separately confirmed detailed diagnostic option can include full paths, so inspect what you share.

The app used in this guide

Just Converter

View app details

Related guides

Sources and further reading