Use Kynd’s 6.1 GB Z-Image Turbo 4-bit MLX pack on any supported Apple Silicon Mac with 16 GB or more unified memory. Kynd installs that route in-app. A roughly 20.7 GB BF16 pack is for 32 GB or larger Macs, but it currently requires a compatible local conversion and is detected—not installed—by Kynd.
Z-Image Turbo is unusually approachable for a capable local image model. The official 6B Turbo release is distilled to eight model forwards; Kynd’s local request recipe exposes this as a nine-step generation.
The model and working tensors still share memory with macOS, the Kynd interface and any loaded chat model. Kynd uses a memory lease around generation and unloads the image service after idle time, so a local image session does not have to pin that memory forever.
16 GB Choose the recommended 4-bit MLX pack. Start at 768px if other large models are open; 1024px is the normal target when memory is free.
Which Z-Image model should you run?
For most Mac users, there is one simple answer: the 4-bit MLX pack. It is the route Kynd can provision, resume and support end to end.
What Kynd currently supports.
Native MLX generation
The preferred service runs on Apple Silicon and keeps the image path local. Kynd provisions its pinned runtime instead of depending on a global Python install.
4-bit recommendedIn-app model setup
The 4-bit model has visible progress, cancellation and resumable downloading. Kynd checks free disk space and keeps extra staging headroom.
≈ 6.1 GB + 3 GB headroomPrompt controls
Use a seed, 1–12 steps and square or landscape sizes from 256 through 1344 pixels, in multiples of 64.
1024 × 1024 · 9-step defaultLeMiCa cache
The native route exposes slow, medium and fast cache modes for users who want to trade a little iteration behaviour for speed.
Native MLX pathBF16 MLX
Kynd can select a complete compatible BF16 model that you converted locally, but does not currently offer a one-click BF16 download.
32 GB minimumImage editing
This Kynd service is currently prompt-to-image. Do not expect the Z-Image route to edit or inpaint an uploaded frame.
Text to image todayThe practical settings.
1024 × 1024 · 9 steps
- The official Turbo recipe.
- Guidance stays at zero.
- Use a fixed seed when comparing prompts.
- Drop to 768px if memory is busy.
256–1344 pixels
- Width and height use multiples of 64.
- Steps can range from 1 through 12.
- Very wide or tall canvases cost more memory.
- Free chat-model memory before large renders.
How to install and run Z-Image in Kynd.
- 01
Check the Mac
Open Apple menu → About This Mac. The supported Kynd route requires Apple Silicon, macOS 14 or later and at least 16 GB unified memory.
- 02
Open the local image setup
Start an image generation or open Kynd’s model settings. If Z-Image is missing, Kynd presents the local model card and the recommended 4-bit route.
- 03
Install the native runtime and model
Choose Install. Kynd downloads its pinned MLX runtime and the 6.1 GB 4-bit weights with progress you can cancel or resume.
- 04
Begin with the default recipe
Use 1024×1024, nine steps and guidance zero. On a tight 16 GB machine, close other model servers or begin at 768×768.
- 05
Keep the seed when iterating
A fixed seed makes prompt comparisons meaningful. Change one phrase at a time, then raise the canvas size after the composition works.
- 06
Let Kynd return the memory
The local service unloads after its idle window so Metal memory becomes available to chat, code and video again.
Z-Image on Mac FAQ.
Can a 16 GB M1 or M2 Mac run Z-Image Turbo?
Yes. Kynd’s recommended 4-bit MLX pack has a 16 GB unified-memory floor. Keep other large local models unloaded and lower the canvas from 1024px if the machine is under pressure.
Should I use 4-bit or BF16?
Use 4-bit unless you have a specific evaluation reason to compare BF16. It is the supported in-app installation, uses much less disk and memory, and was slightly faster in Kynd’s current M1 Max measurement.
Can Kynd install the BF16 model for me?
Not currently. The BF16 route is detected-only because Kynd does not have a published compatible pack to install automatically. Advanced users can convert the upstream weights to the expected MLX layout.
Does everything stay on my Mac?
Generation runs against Kynd’s localhost image service and local weights. The service is authenticated locally, and Kynd unloads it after idle time to release unified memory.
Where can I verify the upstream model?
See the official Z-Image Turbo model card for architecture, capabilities and terms, and the native MLX implementation used by Kynd’s pinned local path.