# System Requirements

> Discover Aspose.Slides for Java system requirements. Ensure seamless PowerPoint and OpenDocument support on Windows, Linux, and macOS.

Source: https://docs.aspose.com/slides/java/system-requirements/
Updated: 2026-08-02


## **Overview**
Aspose.Slides for Java does not need Microsoft PowerPoint installed, as Aspose.Slides itself is a Microsoft PowerPoint document creation, conversion, page layout and rendering engine.
## **Supported Operating Systems**
Aspose.Slides for Java supports any 32-bit or 64-bit operating system that runs the Java runtime including, but not limited:
### **Windows**
- Microsoft Windows 2003 Server ( x64, x86)
- Microsoft Windows 2008 Server ( x64, x86)
- Microsoft Windows 2012 Server ( x64, x86)
- Microsoft Windows 2012 R2 Server ( x64, x86)
- Microsoft Windows 2016 Server ( x64, x86)
- Microsoft Windows 2019 Server ( x64, x86)
- Microsoft Windows Vista ( x64, x86)
- Microsoft Windows XP ( x64, x86)
- Microsoft Windows 7 ( x64, x86)
- Microsoft Windows 8, 8.1 ( x64, x86)
- Microsoft Windows 10 ( x64, x86)


### **Linux**
- Linux (Ubuntu, OpenSUSE, CentOS and others)

### **Mac**
- Mac OS X

## **Supported Java Versions**
Aspose.Slides for Java supports J2SE 6.0 (Java 1.6) and higher.

## **FAQ**

### Do I need Microsoft PowerPoint installed for conversions and rendering?

No, PowerPoint is not required; Aspose.Slides is a standalone engine for [creating](/slides/java/create-presentation/), modifying, [converting](/slides/java/convert-presentation/), and [rendering](/slides/java/convert-powerpoint-to-png/) presentations.

### Which fonts are needed for correct rendering?

In practice, the fonts used in the presentation or proper [substitutes](/slides/java/font-substitution/) must be available. To ensure consistent rendering on Linux/macOS, it is advisable to install common font packages.

### Why does a custom font render as a fallback or missing text on Linux?

If the font file has inconsistent or corrupted name-table entries, the Linux font-matching stack (FreeType/fontconfig) may select an invalid record, causing the font to be unresolved. Using a font version with corrected name-table records or installing a consistent replacement resolves the issue.