Cloud Architecture
Create cloud architecture diagrams for AWS, Azure, GCP, and more. Design scalable infrastructure with professional cloud icons.
Keep diagrams crisp in Word, LaTeX, and PowerPoint. Learn vector vs raster, DPI requirements, export formats, and how to embed publication-ready figures.
Click Cloud Architecture to open AI Line Studio and generate diagrams from natural language in seconds.
This is the foundation. Get this wrong and nothing else matters.
Vector graphics (SVG, EPS, PDF, EMF) store images as mathematical formulas—points, lines, curves, and shapes. They scale to any size without losing quality. Text remains text. Lines stay sharp.
Raster graphics (PNG, JPEG, TIFF, GIF) store images as a fixed grid of pixels. Zoom in and you see squares. Enlarge them and they blur. Shrink them and they lose detail.
The rule: Use vector formats whenever possible. Period.
For academic papers, vector formats are strongly preferred because:
When to use raster: Only when vector isn't available—screenshots, photographs, or diagrams exported from tools that don't support vector output.
Different publication venues have different requirements. Here are the common thresholds:
| Figure Type | Minimum Resolution | Format |
|---|---|---|
| Line art (diagrams, charts, tables) | 600 DPI | EPS, PDF, TIFF |
| Color/Grayscale figures (photos, complex graphics) | 300 DPI | TIFF, JPEG, EPS |
| Author photos | 300 DPI | JPEG, TIFF |
For IEEE publications, figures need to be submitted in high-resolution formats like EPS, PDF, PNG, or TIFF—PDF files are explicitly not supported as a submission format. Resolution should typically be between 150 and 300 DPI; resolutions above 300 will cause downsampling, and images below 300 won't render well in print.
For line art including tables, IEEE requires a minimum of 600 DPI.
The practical takeaway: Export your diagrams as vector PDF or EPS for submission. If you must use raster, export at 600 DPI minimum for line art, 300 DPI for everything else.
Best: PDF or EPS (vector)
LaTeX with pdflatex prefers PDF for images. PDF can contain both vector and bitmap data, but you want it to contain vector. Use \usepackage{graphicx} to include external graphics.
Workflow for LaTeX:
\begin{figure}[htbp]
\centering
\includegraphics[width=0.8\textwidth]{your-diagram.pdf}
\caption{Your diagram caption}
\label{fig:your-diagram}
\end{figure}
Alternative: Use TikZ to draw diagrams directly in LaTeX. This produces fully vectorized graphics with text that matches your document's font and formatting. The learning curve is steep, but the results are unmatched.
What not to use: SVG is not directly supported by LaTeX or pdflatex.
Best: EMF (Enhanced Metafile) or SVG (if your Word version supports it)
Word handles vector graphics better than it used to. You can insert SVG files directly in recent versions. For maximum compatibility, export as EMF or use the draw.io add-in to embed editable diagrams.
Workflow for Word:
Alternative: Use the draw.io add-in for Word to embed diagrams that remain editable.
Best: SVG or EMF (vector)
PowerPoint preserves vector graphics well. SVG files inserted into PowerPoint remain scalable and crisp at any size.
Workflow for PowerPoint:
For presentation-quality output, target 1920x1080 resolution.
Alternative: Use the draw.io add-in for PowerPoint to embed diagrams directly.
Overleaf's documentation recommends:
Best practice: Export as PDF from your diagramming tool and include it with \includegraphics.
Pro tip: Figures should generally appear before the conclusion section unless they belong in an appendix.
With draw.io add-in (recommended for editable diagrams):
With static image:
With draw.io add-in:
With static image:
If you're spending hours manually arranging boxes and arrows in draw.io or Lucidchart, there's a faster way. AI-powered diagram generators turn natural language descriptions into structured, production-ready diagrams in seconds.
AI Line Studio generates cloud and system architecture diagrams from plain-language descriptions in 15 to 20 seconds. Instead of dragging shapes and aligning arrows, you describe your system—"a 3-tier web app on AWS with RDS and a CDN"—and it produces a complete diagram with 3,000+ officially licensed icons across AWS, Azure, GCP, and OCI.
For research papers and presentations, this matters because:
The tradeoff: AI-generated diagrams may need manual cleanup for complex or ambiguous descriptions. They're a starting point, not a finished product—but they get you 80% of the way there in the time it takes to draw three boxes manually.
1. Exporting as JPEG for diagrams
JPEG uses lossy compression designed for photographs. It introduces artifacts around text and sharp lines. Never export diagrams as JPEG unless explicitly required.
2. Screenshotting instead of exporting
A screenshot is a raster image at screen resolution (typically 72-96 DPI). It will look terrible in print. Always use the export function.
3. Not checking resolution before submission
If you must use raster, verify the DPI. 300 DPI minimum for color figures, 600 DPI for line art.
4. Using PNG when vector is available
PNG is raster. It has a fixed resolution. Use SVG, EPS, or PDF instead.
5. Embedding diagrams as editable objects in final submissions
For journal submissions, embed static, high-resolution images. Editable objects (like embedded draw.io diagrams) may not render correctly in the publisher's system.
| Target | Best Format | Alternative | Why |
|---|---|---|---|
| LaTeX / Overleaf | PDF (vector) | EPS (vector) | Native support, scalable |
| Word | SVG or EMF | PNG (high DPI) | Vector support in modern Word |
| PowerPoint | SVG or EMF | PNG (high DPI) | Scales perfectly |
| IEEE Submission | EPS, PDF, TIFF | PNG | Required formats |
| Web / HTML | SVG | PNG | Scalable, accessible |
| Print (publisher) | PDF or EPS | TIFF (600 DPI) | Vector preferred |
Embedding diagrams in research papers and presentations isn't complicated—but it requires deliberate choices. Vector formats (PDF, SVG, EPS) are almost always the right answer. Raster formats (PNG, JPEG) are for when vector isn't available.
Export at the right resolution. Use the right format for your target platform. And if you're tired of manual diagramming, AI-powered tools can generate publication-ready diagrams from text descriptions in seconds—giving you more time to focus on the research, not the boxes and arrows.