---
title: "PicWay details: collages, editing and sharing"
description: "PicWay isn’t on the App Store yet. Here is how its collages become real Live Photos, how the editor saves your edits, and how saving and sharing work, and why."
url: "https://picway.app/details/create/"
lang: "en"
type: "pages"
updated: "2026-11-05"
published: "2026-11-05"
keywords: "PicWay collage and editing details"
---

# PicWay details: collages, editing and sharing

URL: https://picway.app/details/create/
Markdown: https://picway.app/details/create/index.md
Last updated: 2026-11-05

PicWay details for collages and editing explain the small decisions behind the iPhone photo app that isn’t on the App Store yet: how a collage is saved as a real Live Photo or falls back to a still, where saved collages go, how the editor handles borders, HDR and full-size originals, and how sharing, format copies and Shortcuts work.

PicWay is coming to the App Store soon; it isn’t there yet. Making something from your photos is only worth it if the result is what you meant: a Live Photo that is really a Live Photo, an edit that saves what you saw, and a share that goes through without a hitch. Here are the details behind PicWay’s collages, editor and sharing, each with what it does and why it was built that way. For the rest of the app, see [PicWay details](https://picway.app/details/).

## What happens when you save a collage that moves? {#collage-motion}
A collage that contains Live Photos can move, and keeping it a real Live Photo after saving is harder than it sounds.

### The export panel has three choices, and the Live Photo line tells you how it will play {#collage-modes}

**What it does.** When a collage contains Live Photos, the export panel offers three choices: Live Photos, Video and Still image. The line under the Live Photos choice follows the way your collage moves. All at once reads “Touch and hold to play”; One by one reads “Touch and hold to play them in turn, with sound”; Spotlight reads “Touch and hold to spotlight one, then back to the collage”.
**Why it works this way.** One by one and Spotlight behave differently when you touch and hold, and the line is there so that you don’t find that out only after you have the finished collage.

### A collage can carry Live Photos: it goes into your library as a Live Photo {#collage-live}

**What it does.** When a collage contains Live Photos, you can export it as a Live Photo: a still image and a video, tied together by one shared ID. Both are handed to your photo library in the same save request, so, once they pass the check described next, the library stores them as a Live Photo.

**Why it works this way.** A Live Photo is a pair of files that only belongs together because of that ID. PicWay would rather fall back to a plain still than leave a collage that looks saved but isn’t really a Live Photo.

### Before it saves or shares, PicWay checks that the pair really is a Live Photo {#collage-verify}

**What it does.** Before saving or sharing, PicWay asks iOS to put the still and the video back together as a Live Photo. Only if iOS accepts the pair is it delivered as a Live Photo.

**Why it works this way.** If a pair can’t be put back together, handing it over anyway would give the other person a picture and a separate video that look unrelated, which is worse than sending a single still poster.

### If the check fails, you get an ordinary still, never a fake Live Photo {#collage-fallback-still}

**What it does.** If the pair doesn’t pass, PicWay removes the shared ID from the still, deletes the paired video and saves only an ordinary still image. If the ID can’t be removed, it shows an error instead of saving a fake Live Photo.

**Why it works this way.** A picture that still carries the ID is treated as half a Live Photo whose other half never exists. With only two choices left, a fake Live Photo or an error, PicWay chooses the error.

### With no Live Photos in the collage, the motion choices turn into a still {#collage-no-live}

**What it does.** If the collage has no Live Photos, a request for the Live Photo or Video export is turned into an ordinary still image.

**Why it works this way.** The video builder can’t run with nothing to animate. Falling back to a still turns what would have been a failed export into a valid one.

### If one Live Photo’s motion can’t be read, only that cell stays still {#collage-missing-clip}

**What it does.** When the paired video of one photo in the collage can’t be fetched, only that cell uses its still image and the rest keep moving. If none of them can be read, the whole collage becomes a still.

**Why it works this way.** One missing clip shouldn’t cost you the motion of every other cell. When there are no clips at all, there is nothing left to animate, so the whole collage steps down.

### Choosing Video exports an mp4 and doesn’t pretend to be a Live Photo {#collage-video-mp4}

**What it does.** The Video choice exports an mp4 with no shared ID, so iOS never mistakes it for half a Live Photo. Creations keeps the poster still of that work; the video itself goes wherever you sent it, to Photos or into a share.

**Why it works this way.** Creations treats an entry with a paired video as one that can be played by touching and holding. Putting an mp4 there would make that fail later, when you open it, far from where the mistake was made.

### “Couldn’t create” and “damaged” are two different messages {#collage-errors}

**What it does.** When a Live Photo can’t be assembled, a timeout and a pair that doesn’t match say different things. A timeout reads “Couldn’t create the Live Photo” and “Live Photo timed out. Try again later.” A pair that doesn’t match reads “Couldn’t create this Live Photo” and “Live Photo motion is damaged; use it as a still only.” Collages wait up to 45 seconds; sharing a screenshot poster waits 8 seconds by default.

**Why it works this way.** Before, a timeout was reported as a damaged original, so people thought the work was ruined when tapping again would have fixed it. The 45 seconds is not a promise to wait forever: closing the panel or running out of background time stops it at once. The number only keeps PicWay from giving up on a pair that would have assembled.

## Where does a saved collage go, and what if the save is interrupted? {#collage-saving}
These details are about what happens while a collage is being saved.

### Every collage lands in one album: PicWay Creations {#collage-album}

**What it does.** Live Photo, video and still collages all go into one album, PicWay Creations, and appear in Creations. They don’t inherit the albums of the source photos, and the location is left empty. Sharing also saves a copy there first; if that save fails, the share still goes ahead.

**Why it works this way.** A collage is built from several photos, so it has no single location, and an empty one is the right answer. The album gives collages a home of their own, so Creations can find them there.

### Tap Save to Photos, then leave: it carries on and tells you when it’s done {#collage-background}

**What it does.** After you tap Save to Photos you can close the editor. The export runs in the app, not on that screen, and if you switch to another app it uses the extra time iOS gives it. If you’re away for at least 30 seconds and have allowed notifications, you get a notification when it finishes (or fails). PicWay never uses this moment to ask for notification permission.

**Why it works this way.** Tapping Save and switching away at once is a different situation from tapping Save and waiting 20 seconds before leaving, so the 30 seconds are counted from the moment you leave the app. A notification for a quick glance at another app is only noise, and enough of that could make you turn notifications off, which would also turn off the daily review reminder.

### Only one save runs at a time, and tapping twice runs it once {#collage-one-at-a-time}

**What it does.** Only one collage save runs at a time. If you tap Save again for the same photos with the same settings, it runs once.

**Why it works this way.** An export fetches a dozen or more originals and then composes frame by frame, and two of those at once would fight over memory and the video encoder.

### If one photo can’t be fetched, its cell turns grey and the rest still export {#collage-missing-photo}

**What it does.** If one of the originals can’t be fetched, say because it hasn’t come down from iCloud, that cell is drawn in neutral grey and the rest of the collage exports as usual. A missing photo only makes the export fail if none of the photos can be fetched. PicWay first asks for the photo at the size the collage needs, which may mean fetching it from iCloud; if that doesn’t arrive, it makes one more try using only what is already on the phone, and gives up if there is no progress for 3 seconds.

**Why it works this way.** A grey cell is much better than losing the whole collage. If nothing can be drawn, there is genuinely nothing to deliver.

### A long strip is drawn cell by cell instead of all at once {#collage-long-strip}

**What it does.** A long strip collage doesn’t decode all its photos up front. It fetches them cell by cell and releases each one once it is drawn.

**Why it works this way.** In an internal measurement on one test load, peak memory was 365 MB when everything was held at once and 12 MB when drawn in sections.

### The exported video never goes below 12 Mbps and grows with the canvas {#collage-bitrate}

**What it does.** The collage video is encoded at a bit rate that scales with the number of pixels: 12 Mbps for a 1080 × 1440 canvas, never lower than that, and never higher than 64 Mbps.

**Why it works this way.** Keeping the same amount of data per pixel as the canvas gets bigger stops a large collage from looking thinner than a small one. The cap keeps the file size and the load on the encoder under control.

### When PicWay offers a collage after Review, a Live Photo needs its video already on your phone {#collage-suggestion}

**What it does.** At the end of a Review round PicWay may offer to make a collage from photos you went through. A Live Photo only qualifies if its video part is already on the iPhone. PicWay checks that without going online, and counts the video as not on the phone if it can’t tell within 10 seconds.

**Why it works this way.** With Optimize iPhone Storage on, it is common for the still to be on the phone while the video is still in iCloud. Without this check, a Live Photo in the offered collage would not move when you touch and hold, and playing it spun for 15 seconds before giving up. Downloading originals from iCloud stays something you start yourself in the editor.

## What does the editor do with Live Photos, filters and your originals? {#editing}
Editing changes your photo, so the editor is careful about what it overwrites and what it tells you.

### Add a frame to a Live Photo and it is saved as a still {#border-live}

**What it does.** When a Live Photo has a border (the Frame tool in the editor), the result is always saved as a still image, no longer a Live Photo. The original stays in your library, and reverting to it brings the Live Photo back.

**Why it works this way.** A border makes the still image bigger, but the video frames would still be drawn at their old size, so touching and holding crops the video, pushes it into a corner or shows junk colours. A vertical Live Photo stores its video sideways, which makes it worse. This was tried on real iPhones over several versions without getting around it, so it ended up as a rule.

### Pick any moment of a Live Photo and save it as a photo, with your edits {#live-key-frame}

**What it does.** In the editor’s Live page you drag to the frame you want and tap Save as photo. A separate photo is added to your library with your current edits applied, and the original Live Photo stays as it was. Make Key Photo sits under the same filmstrip.

**Why it works this way.** What you see on the screen is what you press the button for, so the saved frame carries the same crop and colour edits. The frame is rendered by the same function that renders each frame when you save the Live Photo itself, so “look first, then save” and “save straight away” can’t produce two different pictures.

### Filters you used recently are moved up, and are not repeated in their group {#filter-recent}

**What it does.** On the filter strip, the last few filters you used come right after the original (once you have used some). They are moved out of their original groups, so each filter appears once on the strip. The order is set when you open the page and doesn’t shuffle while you tap filters.

**Why it works this way.** Seeing the same filter twice makes you wonder why it’s there again. Moving the cells is also less risky than reordering them live: the one under your finger would run away. The smallest group still has 6 filters, so no group can be emptied this way.

### Your own filters always have a place, even before you have saved one {#filter-custom}

**What it does.** The Custom filters section is always on the strip, even with no saved filter. Its last cell is Save filter, and a saved filter lives in that section.

**Why it works this way.** The entry for saving lives inside that section. If the section disappeared whenever it was empty, your first save would have nowhere to go.

### While you drag a slider, the preview keeps up with your finger {#slider-preview}

**What it does.** When you drag a slider or straighten a photo, the preview renders one picture at a time and throws away the values in between. As soon as one render finishes it goes straight on to the latest value, so the picture follows your finger and ends on the latest value.

**Why it works this way.** In an internal measurement on an iPhone, made before this was changed, a drag took 211–623 ms and sent 7 to 21 preview requests, but only 0 to 2 of them rendered, because every request was cancelled by the next one. The picture then sat still while you dragged and changed only on release, although one render takes just 1–73 ms.

### If HDR can’t be kept, PicWay asks before saving it as SDR {#hdr-consent}

**What it does.** When you save a photo and its HDR layer can’t be kept, PicWay doesn’t quietly save a plain SDR picture. It stops and asks first, and it saves as SDR only after you agree. When the HDR layer can be kept, you aren’t asked anything.

**Why it works this way.** A silent downgrade used to be possible: a rotated or cropped photo with an HDR layer came back as SDR while the screen said Saved. Refusing to save would be wrong the other way round, because you want to be able to edit HDR photos. A downgrade that costs something should be confirmed first.

### Before an edit overwrites a photo, PicWay checks it holds the full-size original {#edit-full-size}

**What it does.** Saving an edit writes new pixels over the photo in your library. Before it does, PicWay confirms that iOS gave it the full-size original and not a small stand-in. If it can’t be sure, it doesn’t write.

**Why it works this way.** Saving an edit is the path that writes over an existing photo, and it used to have no check on whether what came back was big enough. When it isn’t clear, writing nothing is safer than writing the wrong thing.

## How do sharing, format copies and Shortcuts work with the rest of iOS? {#sharing-converting}
These are the places where PicWay meets the share sheet, Shortcuts and your photo library.

### Sharing a Live Photo collage still shows AirDrop {#share-airdrop}

**What it does.** When you share a Live Photo, the share sheet hands iOS a single item, so AirDrop appears among the targets. AirDrop receives the still image as a file; other targets, such as Messages, receive the Live Photo itself. If the pair wasn’t assembled, everything receives the still.

**Why it works this way.** A tester once reported that sharing showed no AirDrop. The cause is that AirDrop only handles files, and a Live Photo object isn’t one. Handing over two files so that AirDrop could rebuild a Live Photo was tried and removed: the sheet showed two items, and the idea that the receiving Photos app would merge them had never been checked between two iPhones.

### A shared Live Photo poster shows your edited version {#share-poster-edited}

**What it does.** When you share a poster of a Live Photo, for example from a screenshot share, it shows the version you’re looking at, edits included, not the unedited original. If the Live Photo version can’t be made, you still get an ordinary still poster.

**Why it works this way.** iOS can hand back either the original with a set of edit instructions to replay or a finished picture with the edits already applied. PicWay asks for the finished picture, because replaying the instructions would export an unedited Live Photo that doesn’t match the card on your screen.

### Format conversions make a copy in PicWay Conversions and leave the original alone {#format-copies}

**What it does.** Changing a photo’s format, turning a video into a Live Photo and turning a video into a GIF each make a new copy and leave the original untouched. The copies go into the PicWay Conversions album and, as far as possible, keep the shooting date, location, favourite flag, original albums and PicWay tags.

**Why it works this way.** All three conversions share one place where a copy is written into the library. When the video-to-Live-Photo and video-to-GIF conversions each wrote their own copy, details were missed without any error: the album, the “registered” step and the banner that opens the conversions folder. A single path makes that much harder to repeat.

### In Shortcuts, PicWay’s action is named PicWay, not “Open” {#shortcuts-name}

**What it does.** In the Shortcuts app, PicWay’s action, the default name of a new shortcut and the name matched by search are all “PicWay”, and “Open” is only the parameter’s name. A row therefore reads “PicWay · Open: On this day”. Searching for photos, review or albums finds it too.

**Why it works this way.** The action used to be called “Open”, so a shortcut saved with its default name was called “Open”, lost among dozens of others, and searching for the app’s name found nothing. The extra search words cover what you are likely to type first.

### Shortcuts can only open screens, never act on a specific photo {#shortcuts-navigation}

**What it does.** The actions PicWay exposes to Shortcuts only open a screen. There are 12 destinations, among them On this day, Random, Journeys, Collage, Make a card, Creations and Edit photo. Actions that touch a specific photo, such as keeping this one or setting it aside, exist only on the widget.

**Why it works this way.** Those actions need the widget’s own proof of which photo it was showing. The screens PicWay opens ask you to choose your photos themselves, so a shortcut never carries a photo’s identity into the app.

### The Share Sheet’s Compress, Collage and Live Photo rows just open PicWay {#share-actions}

**What it does.** Compress, Collage and Live Photo appear as rows in the system share sheet. Collage shows up when you select 2 to 30 photos, and Live Photo when you select one video. Tapping a row doesn’t process anything in the share sheet: the sheet closes and PicWay opens.

**Why it works this way.** The work is done in PicWay itself, where you can see it and keep going. The extension’s screen is transparent, so all you see is the sheet closing and the app opening.

## Keep reading {#more}

- [PicWay details](https://picway.app/details/): the other parts of the app
- [How to make a Live Photo collage that really moves](https://picway.app/guides/live-photo-collage/)
- [How to save photo edits as a filter on iPhone](https://picway.app/guides/save-photo-edits-as-filter-iphone/)