Short answer
Teams does not keep the order you select images in. A Microsoft moderator confirmed in June 2026 that this is “currently expected”: when several images go in one message, Teams uploads them in parallel, and the preview order follows how the files are handled, not the order you picked them. There is no setting for it. The workarounds Microsoft suggests are to send them one by one, to number the filenames 01, 02, 03, or to combine them into one PDF.
Use PicOrder. It stamps 1, 2, 3 into the photos and names the files 01, 02, 03, which is the fix Microsoft’s own moderator suggests, done for the whole batch at once. Try it free in your browser →
What Microsoft says
The clearest statement is a thread on Microsoft Q&A titled “When sending multiple photos on Teams, the preview order ends up completely wrong”, posted on 23 June 2026. A Microsoft External Staff moderator answered the same day:
“This is currently expected with Microsoft Teams. When multiple images are attached in a single message, Teams processes and uploads the files in parallel, and the preview order is determined by how the files are handled internally rather than the order in which they were selected.”
And, in the same answer: “At this time, there is no built-in option to manually control or preserve the ordering of images in the preview.”
Two caveats, to be fair to Microsoft. This is a moderator’s answer on a support forum, not a page of product documentation, and Microsoft’s documentation does not mention image order at all. Teams’ published limits say only that a chat message can carry up to 10 file attachments. But it is the only statement on record, and it says the scrambling is the product working as built.
Why parallel uploads scramble the order
Uploading files in parallel is a sensible way to make a batch send faster. Five photos go up at once rather than one after another. The side effect is that they finish in whatever order the network lets them: a small photo can overtake a large one, and two photos of the same size can swap places from one send to the next.
If the preview is built from the files as they finish, the order you tapped them in never makes it into the message. That is why the problem looks random, and why selecting more carefully makes no difference.
A different problem: new photos mixed with old ones
In the same thread, the person who asked later clarified that their real issue was different: new photos were appearing mixed in with photos from older messages. The moderator called that “unexpected behavior and not how Teams is intended to function”, and suggested checking Teams on the web, signing out and back in, clearing the Teams cache and updating the app.
So check which problem you have. If photos inside one message are out of order, that is the expected behaviour above and clearing the cache will not change it. If photos are leaking between messages, that is a fault, and those troubleshooting steps are the place to start.
The three workarounds, compared
The moderator’s answer lists three. Each one works; they differ in what they cost the person reading.
| Workaround | What it costs | Best for |
|---|---|---|
| Send one at a time | A message per photo. Ten photos fill the chat, and anyone replying in between breaks the sequence. | Three or four photos. |
| Number the filenames 01, 02, 03 | Renaming by hand on a phone is slow. The previews may still be shuffled; the names tell the reader the real order. | Anyone who will download the files. |
| Combine into one PDF | An extra step and an extra app. The reader has to open the PDF to see anything. | Formal reports that get filed. |
Use two digits, not one. Files named 1 to 12 sort as 1, 10, 11, 12, 2 in most file lists, including OneDrive, where Teams keeps files shared in chats. Microsoft’s community forum has a long thread on exactly that, and the fix is a leading zero.
There is a fourth option that combines the first two: put the number in the picture. A photo with a 3 in the corner reads as the third photo in the preview, in the downloaded file, and when someone forwards it to a client, whatever order Teams shows them in.
Discord and Slack
Discord documents that several images in one message are “sent together and displayed as a mosaic format”, and says nothing about the order of that mosaic. Users have asked for it on Discord’s own feedback forum, in a request titled “Send pictures in the order you select them”, and others there describe several images uploading at once and landing out of order. That is the same parallel-upload pattern as Teams, reported by users rather than confirmed by Discord. The same fixes apply: one at a time, numbered filenames, or numbers in the picture.
Slack is the exception. Its help centre says that after you drop up to 10 files into a message, you can “drag and drop the file previews to reorder them” before sending. That is documented for the desktop app. Check the previews before you press send.
For how a dozen other apps compare, see which messaging apps keep your photo order.
For site reports and inspections
Teams is where a lot of work photos go: a site walk, a snagging list, an inspection, a before-and-after for a manager. These are the photos where the order carries the meaning. Photo 4 is the crack, photo 5 is the same crack after the repair, and a reader who sees them swapped draws the wrong conclusion.
- Refer to photos by number in the message. “See 4 and 5” works only if the numbers are on the photos.
- Keep your numbered copy. When someone replies a week later about photo 7, you both mean the same one.
- Keep the set small per message. Teams takes up to 10 attachments in a chat message, so a 30-photo walk is three messages. Number across all three, 1 to 30, so the set still reads as one.
The construction progress guide covers the same problem for site photos sent to a client.
Numbering the batch in one go
- Open PicOrder in your browser, on a phone or a work laptop, and add the photos.
- Pick or drag them into the order the reader should follow.
- Download. Each photo has its number in the corner and a filename starting 01, 02, 03.
- Attach them to the Teams message. However the previews line up, the numbers give the order.
Nothing is uploaded: the numbering happens on your device, which matters for photos of a client’s site or a claim. If you only want the filenames and not a number in the picture, the free rename tool does that part on its own.
Common questions
Why does Teams send my images in the wrong order?
A Microsoft moderator explained in June 2026 that when several images go in one message, Teams processes and uploads them in parallel, and the preview order is decided by how the files are handled internally rather than the order you selected. Microsoft described it as currently expected.
Is there a Teams setting to keep the image order?
No. The same Microsoft answer says there is no built-in option to control or preserve the order of images in the preview.
Will clearing the Teams cache fix it?
Not for images out of order inside one message, which Microsoft says is expected. Clearing the cache, signing out and updating were suggested for a different fault, where new photos get mixed in with photos from older messages.
What does Microsoft suggest instead?
Three workarounds: send the images one by one, rename the files with a numeric prefix such as 01, 02, 03, or combine the images into a single document such as a PDF before uploading.
Does Discord have the same problem?
Discord documents that several images in one message are shown as a mosaic and says nothing about their order. Users on its feedback forum have asked for images to be sent in the order they select them. The same fixes apply: one at a time, numbered filenames, or numbers in the pictures.