Cloud Icons Guide

Cloud icons for PowerPoint: the workflow that survives a projector

By the engineer who builds Datadef, from client work on data platforms · Reviewed August 21, 2026

The architecture slide is the one everybody photographs and nobody can read. Two causes account for most of it: an icon inserted as a small raster and then scaled up, and a label set at a size that works on a laptop and vanishes at the back of a room. Both are fixable in the ten minutes before the deck goes out.

Try it free
6 min readFor anyone presenting a cloud architecture from slides

See it as a diagram

Everything below, as a diagram you can edit. Describe yours and see it in seconds.

172/2000• 3 credits left
Try:

No account needed · Editable canvas, not a picture

The 32 pixel trap

The AWS asset package sorts service icons into size folders, commonly 16, 32, 48 and 64. People open the 32 folder because 32 sounds like an icon, take a raster out of it, drop it on a slide and drag it to 120 points. That is a four-times upscale, projected at 1920 across a wall, and it is the single most common cause of the unreadable architecture slide.

Insert the SVG instead and the arithmetic disappears. PowerPoint keeps an inserted SVG as vector artwork, so the scale factor stops mattering entirely and the size folder decides only which level of detail the artwork was drawn at. Hold Shift while dragging a corner handle so the aspect ratio survives.

Azure has no version of this trap, because Microsoft ships the set as SVG only with no raster alternative in the download. What it adds instead is a rule about the resize itself: the published terms say not to crop, flip or rotate icons and not to distort or change icon shape in any way, which turns the Shift-drag habit into a condition of use rather than a preference.

A deck icon spec, decided once

The reason architecture slides look assembled rather than designed is that every icon got its size from whatever the mouse did. Fix one spec at the start of the deck and apply it to every slide. Consistency reads as competence at a distance where nobody can see the detail anyway.

Labels are half the spec. Microsoft recommends including the product name somewhere close to the icon in its Azure diagram guidance, and the same rule saves every deck: at projection distance an icon is a coloured square and the word underneath is what identifies it. Fourteen points is the floor, directly beneath the icon, product name spelled out rather than abbreviated on first use.

Do not put more than about twelve components on one slide. If the architecture needs more, the slide becomes two slides or a zoom sequence, and that decision is easier while building than while presenting.

Deck icon spec (choose once, apply everywhere)
  icon box       64 x 64 pt, SVG, never scaled without Shift
  label          14 pt minimum, directly under the icon
  label text     product name spelled out (Simple Queue Service, not SQS)
  spacing        at least one icon width between unrelated components
  icon source    one vendor release, stamped on the appendix slide
                 (AWS 07312026 / Azure_Public_Service_Icons_V24)
  components     12 per slide maximum

The slide is a snapshot, and that is the real problem

A deck is a fork in the road. The moment it is exported, the architecture it shows stops tracking the architecture that exists, and the same slide gets reused for a year because rebuilding it is an afternoon.

A cheaper arrangement: keep the diagram in one place, and treat the slide as a render of it. Datadef exports PNG and JPEG from the canvas, so refreshing the slide before a presentation is one export and one paste rather than an afternoon of nudging shapes. Where the deck lives somewhere that renders images from a URL, a live embed removes even that step.

Pick the export width from the projector, not from the laptop. A slide filling a 1920-wide projected frame wants an export at least 1920 across, and a diagram that occupies half the slide still wants close to that if anyone will zoom into it afterwards. The number that goes wrong is always too small: an export sized to look right in the editing window is roughly half of what the room needs.

For repositories, the loop closes completely: repository sync regenerates the diagram from a connected branch, so the picture you export the morning of the meeting reflects what merged, not what you remembered.

Building the slide diagram without hand-placing shapes

Hand-placing an architecture in PowerPoint is a two-hour job with a poor finish, because the tool is not a diagram editor. The alternative is to describe the architecture in one paragraph, have the components drawn with their real marks from a 2,098-file icon library, then adjust zones and edges on a canvas built for it and export once.

Start from the prompt on this page, or from a closer starting point in the template gallery. Icon choice happens during generation from one library, so the deck inherits a single consistent set rather than whatever four different downloads happened to contain. Exports are PNG and JPEG; PNG is the one to use, because JPEG has no transparency and puts compression artefacts around the hard edges and thin text a diagram is made of.

FAQ

How do I add AWS icons to PowerPoint without losing quality?

Insert the SVG rather than a raster. PowerPoint keeps SVG as vector artwork, so it stays sharp at any size, while a raster taken from the 32 pixel folder and dragged to 120 points on a slide is a four-times upscale and looks like one when projected. Hold Shift while resizing so the aspect ratio is preserved.

What size should cloud icons be on a slide?

Pick one size and use it for the whole deck. A 64 by 64 point box works for most 16:9 layouts, with the product name at 14 points or larger directly underneath. The specific number matters far less than every icon on every slide sharing it.

Should I use the AWS PowerPoint toolkit or the icon package?

AWS publishes both from the same page and both carry the marks of the same release, so the choice is only about where you start. The PowerPoint toolkit gives you icons already laid out on slides. The icon package is the general format set, better when you are building your own layout and want to insert only what you need at the size you chose.

Are Azure icons available in a PowerPoint or Visio format?

No. The Azure Architecture Center states the icons are not provided in Visio stencil format, that they are general purpose SVG files you drag into Visio and other tools, and that there are no plans to provide stencils. One useful side effect: there is no raster file in the Azure download to pick by mistake.

How do I stop an architecture slide from going out of date?

Keep the diagram in one place and treat the slide as a render of it rather than the original. Re-exporting a PNG before a presentation takes seconds; rebuilding a hand-placed slide takes an afternoon, which is why nobody does it and the old slide keeps circulating.

Can I export a diagram directly into a deck?

Export the diagram as a PNG and paste it onto the slide. Exports are PNG and JPEG, and PNG is the right choice for a diagram because JPEG has no transparency and puts compression artefacts around exactly what a diagram is made of, hard edges and thin text. Size the export from the projector width rather than from the editing window.