Midjourney Alpha: October Workflow Changes

Midjourney's early October Alpha update makes project settings and image review easier to manage. It does not announce a new image model. Which settings can you trust to stay in place? Which details should you still record before handing work to someone else? Those are the useful questions for this update.

Updated October 13, 2026: this review combines the October 1 changelog with the October 7 changelog, published October 8. It describes the Alpha website, not a promise that another service has the same features. The workflow suggestions are editorial recommendations, not controlled test results.

Folder settings have a defined limit

The October 7 changelog expands the earlier session-only behavior: prompt pills set in a folder now remain across sessions. Treat that as remembered working context, not a guarantee that every prompt, reference or setting synchronizes across all people and devices. Check the active controls against the current brief.

Imagine preparing square product studies in one folder and portrait campaign ideas in another. The folder can help keep those working contexts apart. However, your handoff should still state the intended aspect ratio, model, reference material and any non-default parameters. A colleague cannot recover your intended settings from an attractive finished image alone.

Before a larger batch, inspect the active prompt bar after changing folders. Check the resulting image's recorded settings as well. If they differ from your brief, stop and correct the context before generating more images. This small check is more useful than assuming that a folder name guarantees a complete preset.

Style previews are part of selection, not approval

The September 24 announcement introduced live style previews in the Alpha sidebar. The October changelog says that sending a previewed style now preserves prompt-bar settings. Together, these changes support a clearer path from browsing a visual direction to generating with it.

A preview can help reject an unsuitable style early. It cannot confirm that a final image meets a delivery brief. A small thumbnail may hide an unreadable product edge, an awkward shadow or a busy texture. Keep the subject and composition stable while comparing styles, then examine the generated output at a useful size.

For a lamp campaign, you might compare a soft product photograph with a flat illustration and a textured print. Ask which direction leaves room for copy and preserves the lamp's outline. Do not choose only the most striking preview. The winning style should solve the design goal you started with.

The changelog also describes multiple style references appearing together in one style pill. Hovering reveals their codes. Treat that display as a chance to audit your inputs: remove a reference you no longer intend to use before interpreting a result as a clean test.

Start Creating Now

Editing keeps the base image's proportions

Another October fix concerns aspect ratio. The official changelog says edits keep the base image's ratio, preventing a stray --ar parameter from stretching the result. That separates a common editing task from a generation task: changing an object's appearance should not silently reshape the approved frame.

It does not mean an edit automatically produces every crop needed for a campaign. If the deliverable changes from a landscape banner to a portrait poster, plan that composition separately. Confirm the exported dimensions, subject placement and available space for text. A preserved ratio is useful, but it is only one part of a production check.

Likewise, the September announcement describes improvements to targeted edits and repeated editing. Attribute that claim to Midjourney rather than assuming every image will remain perfect. Compare the base and edited versions, including areas you did not intend to change. Faces, lettering and product markings still deserve close inspection.

The release notes also cover search, lightbox navigation and filters. Search starts Create and Explore feeds from the top; Back restores the page you were viewing. Filters clear when switching between Organize and Create. These are interface behaviours, not changes in image quality.

For someone reviewing a long project history, the distinction matters. A changed filter can alter which images appear without deleting anything. Before concluding that a frame is missing, check the current view, folder and filter state. Record the image identifier or save an approved export when a particular result matters to a handoff.

The same logic applies to moodboard errors. The changelog says a private moodboard belonging to someone else now produces a clearer explanation. That message does not grant access. A shared code and permission to use its contents are different things; ask the owner for an appropriate shared reference instead of treating the error as a prompt problem.

A handoff should survive the browser session

Keep a small text record beside approved outputs. Include the brief, prompt, reference roles, model setting, intended ratio and selected image. Add any issue that changed your decision. This record can live in your team's normal document or asset system; it need not depend on an unverified feature of an image platform.

For example, write: “Ceramic lamp, warm neutral background, portrait placement with clear space above; reject outputs with a hidden switch.” That note is more useful than “use the best version.” It gives the next reviewer a reason for the selection and a concrete failure condition.

At the next session, open the correct folder and compare its settings with the saved record. Run a small check before a larger production batch. If the interface has changed, revise the procedure from what is actually visible rather than relying on an old screenshot.

What remains a plan

Shared folders are now available in Alpha, with collaborators who can generate and viewers who can browse. The October 7 changelog supersedes the earlier collaboration roadmap. Persistent edit history is still listed as upcoming; do not treat it as released.

The practical improvement today is clearer control over working context. Use the interface conveniences, but save enough information to reproduce your intent outside one browser tab. Our Alpha workspace guide covers broader organisation, while the editing guide explains how to compare an edit against its base.

Sources: October Alpha changelog and September editing and preview announcement.

October 7 update.