# FLUX.2 Turbo vs Flash Guide: fal APIs and Local LoRA Access > Published 2026-04-01, updated 2026-09-05 · https://www.promptzone.com/niamh_wu/flux-2-turbo-flash-speed-and-power-in-ai-imaging-2j08 --- title: "FLUX.2 Turbo vs Flash Guide: fal APIs and Local LoRA Access" published: true description: "Compare FLUX.2 Turbo and Flash APIs on fal, and learn what the downloadable Turbo LoRA needs for local use." tags: ai,imagegeneration,comfyui,flux --- FLUX.2 Turbo and FLUX.2 Flash are separate fal offerings based on Black Forest Labs’ FLUX.2 dev image model. Both have hosted endpoints; Turbo also has a downloadable LoRA that requires the dev base model, while the cited Flash documentation offers hosted access only. [Turbo API][turbo], [Flash API][flash], [Adapter card][adapter] ## What are the key facts about FLUX.2 Turbo and Flash? | Field | Verified detail | | --- | --- | | Developer | Black Forest Labs develops FLUX.2 dev; fal provides the Turbo adapter and hosted Turbo/Flash services. [Base card][base], [Adapter card][adapter], [Flash API][flash] | | Released | Base FLUX.2 dev: November 25, 2025. Turbo and Flash release dates: not published in the cited endpoint documentation. [Base release][launch], [Turbo API][turbo], [Flash API][flash] | | Type | Hosted image-generation endpoints; Turbo additionally has a downloadable distillation LoRA. [APIs][turbo], [Adapter card][adapter] | | Size or parameters | Base dev image transformer: 32 billion. Separate Turbo adapter and Flash deployment counts: not published in the cited cards. [Base card][base], [Adapter card][adapter], [Flash API][flash] | | License and access | Turbo adapter inherits the dev non-commercial license; hosted endpoints have separate service access. No open Flash weights are offered in the cited endpoint documentation. [Adapter card][adapter], [Flash API][flash] | | Where it runs | fal infrastructure for the APIs; compatible local FLUX.2 dev implementations for the Turbo adapter. [Turbo API][turbo], [Flash API][flash], [Adapter card][adapter] | ## What do the Turbo API and downloadable LoRA support? The Turbo card provides an eight-step inference recipe, including its custom sigma schedule and guidance setting. This gives local users a concrete configuration to reproduce before making further changes. [Adapter card][adapter] Its repository also includes ComfyUI-compatible adapter weights. The adapter works with the base FLUX.2 dev model, whose weights and supporting components remain part of the deployment. [Adapter card][adapter] The hosted endpoints expose a consistent way to submit text prompts through fal’s client. A developer can evaluate Turbo and Flash by changing the model identifier while retaining a deliberately small request. [Turbo API][turbo], [Flash API][flash] This is useful for measuring the whole application path: submitting a request, waiting for completion, obtaining the image URL, and retrieving the image. Record these stages separately when diagnosing a slow interaction. The underlying FLUX.2 dev model supports generating, editing, and combining images from instructions. Use the appropriate provider endpoint for the task you need. [Base card][base] ## What are the access and deployment limits of Turbo and Flash? An adapter download is only part of a local pipeline. fal’s usage example loads FLUX.2 dev before applying the Turbo weights; downloading the adapter alone does not supply the base model. [Adapter card][adapter] The published eight-step recipe also includes custom sigmas. When attempting to reproduce that example, retain those values instead of treating the step count as the only relevant setting. [Adapter card][adapter] For Flash, the verified access path is fal’s hosted API. Its documentation does not offer an open-weight Flash checkpoint, so plan local deployment around a model that actually has downloadable artifacts. [Flash API][flash] Do not convert an endpoint name into a latency guarantee. Evaluate the image size, concurrency, and end-to-end wait that your application requires; no timings in this article are presented as independent benchmarks. Check the host’s pricing before a paid evaluation. The Flash endpoint lists a megapixel-based charge, so keep output dimensions in your test record alongside the selected model. [Flash endpoint specification][flashspec] The model’s usefulness still depends on the result. Make prompt adherence, visible text, and reference preservation separate review items rather than approving an image solely because it arrives quickly. ## How do you use FLUX.2 Turbo and Flash through fal? Create a fal account and API key, and make `FAL_KEY` available in your server environment. Install the JavaScript client with `npm install --save @fal-ai/client`. Both endpoint guides document this setup. [Turbo API][turbo], [Flash API][flash] Save the following as an ES module in that project. It submits a Turbo request and prints the first returned image URL. [Turbo API][turbo] ```javascript import { fal } from "@fal-ai/client"; const result = await fal.subscribe("fal-ai/flux-2/turbo", { input: { prompt: "A red enamel kettle on a white shelf, soft daylight", }, }); console.log(result.data.images[0].url); ``` To try Flash, change the identifier to `fal-ai/flux-2/flash`. The Flash documentation uses the same client subscription pattern and exposes generated images in its response. [Flash API][flash] Keep the API key in server-side configuration; fal’s authentication guidance cautions against exposing it in a browser or other client-side application. [Turbo API][turbo] After the request finishes, retrieve the image from the returned URL and preserve the endpoint name with the output. Use your own prompt and result filenames so that the test record is easy to compare later. If you need image editing, follow the editing endpoint linked from the relevant model documentation. A text-to-image request should not be treated as an editing request merely because its prompt mentions a photograph. [Adapter card][adapter] For local Turbo use, start with a working FLUX.2 dev installation. Follow fal’s model-card example to load `flux.2-turbo-lora.safetensors`, apply the published sigma schedule, and generate with its documented settings. [Adapter card][adapter] The sibling [FLUX.2 download guide](/thandi_fischer/flux2-ai-powerful-image-generation-model-unveiled-1mib) explains the base-model access decision. The [LoRA pillar](/tara_suzuki/how-to-use-loras-in-comfyui-in-2026-load-stack-and-troubleshoot-235e) supplies workflow background. Use a small representative set of briefs for your evaluation: an object photograph, a composed scene, and an image containing text. Write the pass criteria before generating and keep every result in the comparison. Measure repeated requests instead of timing a single output. Record failures and rejected images, because they affect how long it takes to obtain a usable asset even when successful requests are quick. ## How do Turbo, Flash, and Klein access options compare? | Option | Access distinction | | --- | --- | | FLUX.2 Turbo | fal API plus an adapter download that requires FLUX.2 dev. [Adapter card][adapter] | | FLUX.2 Flash | Separate fal endpoint; no open weights offered by the cited documentation. [Flash API][flash] | | FLUX.2 Klein 4B | A separate BFL model with Apache 2.0 weights and generation/editing support. [Klein card][klein] | If a complete compact checkpoint suits your deployment better than an adapter on dev, read the sibling [Klein checkpoint guide](/eamon_nguyen/flux-2-klein-a-new-powerhouse-in-ai-image-generation-49gn). ## What else should you know about FLUX.2 Turbo and Flash? ### Are FLUX.2 Turbo and Flash the same offering? FLUX.2 Turbo and Flash use different fal endpoint identifiers. Turbo additionally has a published LoRA repository for local use with FLUX.2 dev. [Turbo API][turbo], [Flash API][flash], [Adapter card][adapter] ### Can I run FLUX.2 Turbo locally? fal publishes a FLUX.2 Turbo LoRA for the FLUX.2 dev base model. Its model card supplies the loader, sampling recipe, and inherited non-commercial weight license. [Adapter card][adapter] ### Can I download FLUX.2 Flash weights? The cited FLUX.2 Flash documentation provides hosted inference access through fal. It does not offer an open Flash checkpoint for local installation. [Flash API][flash] ### How should I choose between Turbo and Flash? Compare FLUX.2 Turbo and Flash on the prompts, image sizes, and latency requirements of your application. Use the separate endpoint identifiers in fal’s documentation to keep the results attributable to each service. [Turbo API][turbo], [Flash API][flash] ## Sources - [fal Turbo API documentation][turbo] - [fal Flash API documentation][flash] - [fal Turbo LoRA model card][adapter] - [BFL FLUX.2 dev model card][base] - [FLUX.2 release announcement][launch] - [fal Flash endpoint specification and pricing][flashspec] - [Klein 4B model card][klein] [turbo]: https://fal.ai/models/fal-ai/flux-2/turbo/api [flash]: https://fal.ai/models/fal-ai/flux-2/flash/api [adapter]: https://huggingface.co/fal/FLUX.2-dev-Turbo [base]: https://github.com/black-forest-labs/flux2/blob/main/model_cards/FLUX.2-dev.md [launch]: https://bfl.ai/blog/flux-2 [flashspec]: https://fal.ai/models/fal-ai/flux-2/flash/llms.txt [klein]: https://huggingface.co/black-forest-labs/FLUX.2-klein-4B ## Related guides on PromptZone - [Realistic Photos with FLUX](/stabletom/realistic-photos-with-flux-57aa) - [Best SDXL Models in 2026](/tara_suzuki/best-sdxl-models-in-2026-realistic-anime-and-all-purpose-checkpoints-116)