How to Stop Chat Apps Compressing Your Deck Images

The last slide in the deck looks soft because the picture is a screenshot of a chat preview of an export. Each hop discarded pixels. Slack, Microsoft Teams, and Discord are built to show a fast inline preview. They are not image servers for print or keynote. Windows clipboard history then stores a bitmap if it is under 4 MB — another generation of the same mistake.

The rule: the file that left Figma, Photoshop, or Lightroom is the master. Chat can carry that file. Chat cannot replace it.

What chat apps actually do

Slack. Official help for adding files: upload or share a file; if it is an image, an inline preview appears only when it is under stated pixel limits (Slack documents a longest-side and total-pixel threshold for inline display). A 2018 SlackHQ note stated that desktop uploads keep the original while generating thumbnails. Treat that as "the original *may* still be downloadable from the file object," not as "the pixels on screen are the original." Mobile share sheets and paste-from-clipboard paths are more likely to send a recompressed image. Always download the file from the message's file menu, or better, never depend on Slack as the only copy.

Microsoft Teams. Microsoft documents file sharing through the conversation and OneDrive/SharePoint. Images pasted into a chat are often stored as conversation images with platform-chosen encoding. The durable copy is the file in the team's SharePoint / OneDrive library, not the inline bubble. Prefer Attach / upload over paste when the picture will be reused.

Discord. Fast previews, nitro and channel settings affect size caps. A paste is frequently a compressed upload. Download from the image's Open original style control when it exists, and still keep the design-tool export as master.

None of these vendors document "paste into PowerPoint from our preview at full fidelity." They document files.

The hop that ruins the deck

1. Designer exports hero-16x9-1920x1080.png
2. Pastes into Slack (clipboard bitmap, maybe already smaller than 1920)
3. PM screenshots the Slack bubble
4. That screenshot is pasted into PowerPoint
5. Presenter view on a projector: mush

Microsoft PowerPoint can Insert > Pictures from a file (official training) or paste a clipboard bitmap. Inserting the named PNG is the high-quality path. Pasting a chat screenshot is a new raster of a preview. Presentation Designers: Slide Exports Into a Deck.

PowerPoint for the web even documents that it does not paste pictures copied from Outlook — save the picture, then Insert > Pictures. That is the same philosophy.

Windows history is another compressor

Win+V stores a bitmap representation, capped at 4 MB for history membership. A 1920×1080 32-bit DIB is already in the danger zone. The panel may never show the export. The live Ctrl+V might still paste once — into chat — starting the hop above. Windows Clipboard 4 MB Cap: What Gets Dropped.

Snipping the chat window with Win+Shift+S is a screen-resolution crop. It cannot recover the original file.

The correct paths

Figma: Export, then attach the file. Copy as PNG (officially 2×) is acceptable for a *review* paste, not as the only master. Figma Desktop vs Figma Web: Paste Behavior Differs.

Photoshop: Export As / Quick Export. Best Clipboard Setup for Photoshop Users. After Effects: Save Frame As > File for a still that will be reused; Copy Frame to Clipboard is documented for a quick paste into chat. Motion Designers: Still Frames and Loop GIFs.

Lightroom: Export. Lightroom: When the Clipboard Is Useless.

How to rescue a deck that is already soup

1. Find the original export, Figma frame, or Lightroom catalog
2. Re-export at the size the slide needs
3. In PowerPoint, delete the mushy picture, Insert > Pictures > This Device
4. If the original is gone, download from Slack/Teams as file (not a screenshot of the bubble) and check pixel dimensions in Explorer. If the download is 800×450 and the slide is full bleed, it was never the master
5. Stop pinning the bad bitmap in Win+V

If nobody has the source, say so. Upscaling a chat preview is not a design process.

Studio policy (four lines)

• Chat is a notification with an optional attachment
• Masters live in the project export\ folder, the repo, or the DAM
• Decks and print use Insert/Place from file
• End of week: clear unpinned history so recaptures do not look like sources

Eagle, Billfish, and Asset Managers vs Clip History. Client Feedback: Collect Marked-Up Shots in One Place.

A file shelf can drag the master PNG into PowerPoint or Explorer. Edge-Drop is optional for that drop. If the shelf only holds a bitmap copied *from Slack*, it is part of the problem.

Worked example: fixing Thursday's keynote

The PM built twelve slides from Slack. Five photos look muddy.

1. For each muddy picture, read the filename. If it is image.png or Screenshot …, it is guilty
2. Search the Figma file and export\ for the hero name in the speaker notes
3. Re-export 1920-wide PNG
4. In PowerPoint: delete the picture, Insert > Pictures, pick the export
5. If no source exists, download Slack Open file / download (not a snip). Check width. If it is 800 px, say the master is gone
6. Add a footer note in the project README: "Deck images from export\, never from chat"

Troubleshooting

Soft slides are usually a sourcing error, not a projector error. Keep the export. Attach the file. Insert the file. Leave the chat preview in chat.

Windows limits that add another generation

A Slack preview that is then copied with Win+V becomes a bitmap in a 4 MB box. That is a third or fourth generation before PowerPoint. Inserting the original export skips every generation.

If the only remaining copy is in chat, download the file object, not a snip of the bubble. Check width and height in Explorer details. Slack's help describes inline preview thresholds; what is on screen is not guaranteed to be the upload.

Teams and Discord follow the same honesty test: if the picture cannot be downloaded as a file with a real name, it is not a master. Rebuild from Figma, Photoshop, Lightroom, or AE.

Presenters often defend the soup because "the room will not notice." Projectors and laptop scaling make compression obvious. So do clients who sit close. A five-minute pass that replaces every image.png with an Insert from export\ is cheaper than reprinting leave-behinds. If the deck is already PDF-flattened, go back to the PPTX source, replace, and re-export the PDF. Do not sharpen a flattened mush PDF and call it restored. Working With Print Shops: PDF First, Clipboard Never if those slides become print.

A simple studio rule: if the file name starts with image, Screenshot, or photo_, it is not allowed in a client deck. Rename is not enough -- go get the export. That rule catches 90 percent of the soup without a quality debate.

Related reading

• Motion Designers: Still Frames and Loop GIFs
• Game UI Artists: HUD Icons on a Pull-Tab
• Best Clipboard Setup for Photoshop Users
• Best Clipboard Habits for Developers in 2026

Sources

• Add files to Slack — official file add; inline preview pixel thresholds.
• Insert a picture in PowerPoint (Microsoft) — official Insert Pictures path (training/support family).
• Copy and paste in PowerPoint for the web (Microsoft) — save then Insert when paste from mail is unsupported.
• Using the clipboard (Microsoft Support) — 4 MB / bitmap history.
• Copy a frame to the clipboard (After Effects) — vendor split between clipboard stills and file export.
• Export static designs from Figma — official master-making path.

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support