LocalForge AILocalForge AI
LibraryBlogFAQ

Verify Offline Generation After Setup

First launch may download the engine; generation can run offline afterward. This test separates a completed local setup from features that still need a download.

What this test proves

This procedure verifies one narrow claim: an already-installed LocalForge engine and an already-downloaded compatible model can complete a generation while the computer has no network connection. It does not prove that downloads, updates, support links, or new model acquisition work offline.

Prerequisites

  • Launch LocalForge successfully while connected at least once.
  • Complete any engine download that LocalForge requests on first launch.
  • Install one compatible model and confirm it can produce a small image while connected.
  • Save the model name and basic generation settings.
  • Close unrelated applications that may create confusing network traffic.

Establish a connected baseline

  1. Open LocalForge while the computer is online.
  2. Select the model you plan to use in the offline test.
  3. Generate a small, low-cost baseline image using modest resolution and a batch size of one.
  4. Record the prompt, seed, model, resolution, sampler, and step count.
  5. Confirm that the output file was written and can be opened.
  6. Close LocalForge completely so the next launch begins from a clean state.

Run the offline test

  1. Disable Wi-Fi and disconnect Ethernet. Do not rely on airplane mode if Ethernet remains connected.
  2. Confirm the operating system reports no active network connection.
  3. Reopen LocalForge.
  4. Select the same already-installed model without opening download or update flows.
  5. Reuse the saved baseline settings and generate one image.
  6. Wait for the job to finish, then open the resulting file.

Pass criteria

The test passes when LocalForge launches, loads the local model, completes the generation, and writes a valid output while the machine remains disconnected. The image does not need to be pixel-identical unless every reproducibility setting is controlled; the important result is completion without a network dependency.

If the test fails

  • A download prompt usually means the engine or selected asset was not fully installed before disconnecting.
  • A missing-model error means the chosen file is unavailable locally or stored on a network-mounted path.
  • A permissions error is a storage problem, not evidence that generation requires the internet.
  • A VRAM or driver failure should be retested at lower resolution after reconnecting only if a repair or download is needed.
  • If the connected baseline also fails, repair that baseline before repeating an offline test.

Record the result

Write down the LocalForge version, operating system, model, test date, and result. Repeat this check after major app, engine, model, driver, or operating-system changes. Runs on Windows, macOS, and Linux.

What still needs a network

Offline generation does not make internet-delivered resources local. A new engine component, model, update, documentation page, or support request may still require connectivity. Reconnect intentionally for those tasks, finish the transfer, and repeat the offline test if the local runtime changed.

What to Do Next

FAQ

Does LocalForge need internet every time it generates? +
First launch may download the engine; generation can run offline afterward.
Should I delete or block the app in my firewall? +
No. Start with a reversible Wi-Fi or Ethernet disconnect test so you can distinguish incomplete setup from a firewall configuration problem.
Why did LocalForge ask for a download during the test? +
The engine or selected asset may not have completed its local installation. Reconnect, finish the requested transfer, verify a connected baseline, and test again.
Does an offline test prove that no other software uses the network? +
No. It verifies the LocalForge generation workflow under the tested conditions, not every process on the computer.