manyframeFLUX 1 Schnell.
Explore the declared FLUX 1 Schnell entry through SiliconFlow, with route-specific settings confirmed before the first generation.
Available models and settings are shown in your studio. Review the quote before generating.
The route.
The right inputs.
Start from the creative job, then choose the model and settings that fit it.
Model ID black-forest-labs/FLUX.1-schnell
- Provider path
- SiliconFlow shared image converter, separate from Replicate predictions
- Image size
- Explicit image_size takes precedence over standard size
- Output count
- Explicit batch_size takes precedence over n
- Advanced fields
- Seed, guidance, negative prompt and references need per-model confirmation
Capabilities describe the Manyframe connector. Your studio shows the currently enabled route, supported settings and maximum charge.
Compare FLUX with the provider in view.
A fragrance brief can stay consistent across routes: pink translucent glass, pale stones and hard directional light. When comparing Schnell with FLUX 1.1 Pro, record both the model and provider. This entry uses SiliconFlow’s shared image payload; the Pro entry uses a Replicate prediction request.
Those paths expose different mappings. Replicate’s hd or high quality can enable prompt upsampling, while that mapping is not present in this SiliconFlow converter. Confirm the controls this model accepts, keep the composition consistent and assess the delivered image. The Schnell name does not establish a guaranteed time or price advantage.
Good questions. Clear answers.
Still curious? Browse all FAQs
Can I copy every FLUX 1.1 Pro setting into this route?
No. The two entries use different providers and converters. Confirm supported fields and values on the enabled Schnell route before reusing a request.
What happens if both batch_size and n are present?
A non-zero batch_size takes precedence in the SiliconFlow converter. Use a deliberate count and check the provider’s limit and quote.
Does the common image field guarantee image editing?
No. The shared converter includes image reference fields, but per-model compatibility and edit behavior must be verified with the configured provider.
Keep the FLUX route deliberate.
Record the provider and confirm the accepted settings.