Getting live
Three widths. One site. No extra turns.
The preview pane has three buttons labeled Wide, Mid, and Phone, desktop, tablet-ish, and a narrow column. They resize the same generated HTML; they do not spawn three businesses or spend turns. Most damage happens on Phone: a hero so tall the action is a rumor, hours in a tiny footer, a form that needs pinch-zoom. If you only ever look at Wide, you will publish a site that looks commissioned on a laptop and unusable in a parking lot. After publish, still open the real slug on a real phone; the frame is a width check, not Safari.
Wide, Mid, and Phone are device frames around one preview. Switching them does not spend Cipher turns. Use Phone to confirm the action is tappable. Then open the live slug on a real handset. Frames cannot fake slow radios or notch browsers.
What each label is
Wide is a desktop width for the operator who lives in a browser window. Mid is the awkward in-between of a tablet or a small laptop. Phone is the parking-lot width. All three wrap the same preview document.
What to look for on Phone
Can you tap the action without hunting. Do hours appear before a novel. Is the hero so tall it feels like a billboard with no door. Does NAP wrap into nonsense.
Tap target for the action
Hours visible
Hero not infinite
Form fields usable
What the frame will not tell you
It will not use your customer's thumbs. It will not throttle the network. It will not apply a notch or a browser bar the same way every phone does. It will not prove Core Web Vitals; that is a lab and field topic elsewhere.
How to ask Cipher to fix a width
Say the frame: on Phone the book button is below the fold. Do not say "make it responsive" as if that were a theme checkbox we hid. If only Wide is broken, say Wide. One specific width bug is a better turn than a generic polish request.
QR and Phone are related
A QR on the door lands people on Phone first. If the Phone frame already fails, do not print. Test the live slug with the QR tool after publish. A pretty Wide preview is not a door test.
- Finish facts on Wide
- Switch to Phone
- Try the action
- Send one width-specific fix if needed
- Publish
- Open the slug on a real phone
Mid exists for a reason
Some owners live on iPads at the counter. Mid catches layouts that only break between desktop and phone. If you skip Mid, you might still be fine. Phone is the must. Do not spend a turn "optimizing tablet" as folklore if Phone already works and you have no iPad counter.
Limits and caveats
Frames are CSS widths in the studio, not device labs. They do not spend turns and they do not replace a real handset after publish.
If a sentence would require a competitor SKU we have not verified, or a statistic we did not measure, it does not belong here.
What to do after you read this
If this page answered the query, open Create with the nouns from your own business, not a slogan. If it did not, you are probably in the wrong cluster: go back to the blog hub or Getting live. Do not spin a second URL for a synonym. One intent per page is the whole point of this library.
Tools that actually do this job
These are public pages. Use them when the job is this job. They are not a second product you have to buy.
Questions people actually ask
Does Phone preview emulate iOS Safari?
No. It is a narrow frame. Open the live URL on the phone you carry.
Can I preview a custom domain in the frames?
The studio frames the generated preview. After a domain is connected on Pro, still load the real hostname on a phone.
Why is Mid labeled Mid not Tablet?
The buttons say Mid in the UI. It is the middle width. Do not look for a hidden device lab SKU.
Will overnight jobs change Phone layout?
Restock changes catalog content, not the idea of widths. Layout issues still need a Cipher message.