ASPOSE.SLIDES FOR .NET · THE SAME PACKAGE, ON .NET CORE · NO MICROSOFT OFFICE REQUIRED

PowerPoint files, on .NET Core.

There is no separate .NET Core product, package or download. Aspose.Slides for .NET Core is Aspose.Slides for .NET — the same Aspose.Slides.NET NuGet package, the same download, the same API — resolved against a .NET Core or .NET 6 and later target framework. The same C# creates, edits, converts and renders PowerPoint and OpenDocument presentations on Windows, Linux and macOS, inside your own process, with no Office install and no COM automation.

Download free trial Documentation Same package as the .NET build · full API on trial · evaluation watermark on open and save
Install
CLI
dotnet add package Aspose.Slides.NET
Console
Install-Package Aspose.Slides.NET
Linux and macOS
libgdiplus and fonts on the image; on .NET 6 or later also the System.Drawing.EnableUnixSupport AppContext switch at startup
Other platforms, same object model
RUNS ON

.NET Core, .NET 5, 6, 7, 8 and 9 — the versions Aspose’s system requirements name; .NET 10 is not among them. Windows, Linux, macOS and containers. On non-Windows the standard build needs libgdiplus and the fonts your decks use, whichever asset you bind; the net6.0 asset additionally needs one AppContext switch at startup, System.Drawing.EnableUnixSupport. The Aspose.Slides.NET6.CrossPlatform package removes libgdiplus and the switch on glibc hosts, though every build still needs the fonts. No Office, no COM automation, no display server.

Prefer not to host it yourself? The same work is available as a hosted REST API through Aspose.Slides Cloud.

  • 1

    NuGet package, Aspose.Slides.NET, shared with the .NET build. There is no .NET Core package to look for and no separate .NET Core download.

  • 3

    Target frameworks inside that one package in 26.8.0 — net462, netstandard2.0 and net6.0. A .NET Core project binds to one of the last two on its own.

  • 26.8.0

    Current version on NuGet, published 2026-08-03, and the same version a .NET Framework project resolves. No .NET Core version line runs beside it.

  • 0

    Microsoft PowerPoint installs and Office automation calls in the deployment. Rendering happens inside your own process, with no display server.

Five things people actually write

All examples on GitHub →

Each sample is the whole program, C# as shipped. Pick the job on the left.

PPTX → PDF / HTML / TIFF C#
using Aspose.Slides;
using Aspose.Slides.Export;

using var presentation = new Presentation("quarterly-review.pptx");

presentation.Save("review.pdf", SaveFormat.Pdf);
presentation.Save("review.html", SaveFormat.Html);
presentation.Save("review.tiff", SaveFormat.Tiff);
The same call on Windows, Linux and macOS. The rendering engine ships in the package. Documentation →
STARTUP → RENDERING C#
using System;
using Aspose.Slides;
using Aspose.Slides.Export;

// Once at startup on Linux or macOS, for the net6.0 asset.
AppContext.SetSwitch("System.Drawing.EnableUnixSupport", true);

// A slim image ships almost no fonts, so point the renderer at the ones you deploy.
FontsLoader.LoadExternalFonts(new[] { "/app/fonts" });

using (var presentation = new Presentation("/data/deck.pptx"))
{
    presentation.Save("/data/deck.pdf", SaveFormat.Pdf);
}

FontsLoader.ClearCache();
libgdiplus is needed on the image whichever asset you bind. The switch is required on non-Windows for the net6.0 asset, which uses System.Drawing.Common 6.0.0. It is not needed on .NET Core or .NET 5, where it does not exist. Fonts are needed by every build. Documentation →
PPTX → PNG C#
using Aspose.Slides;

using var presentation = new Presentation("deck.pptx");

for (int index = 0; index < presentation.Slides.Count; index++)
{
    ISlide slide = presentation.Slides[index];

    using IImage image = slide.GetImage(2f, 2f);
    image.Save($"slide-{index + 1}.png", ImageFormat.Png);
}
GetImage(2f, 2f) renders at twice slide size. The parameterless overload returns a small preview instead. Documentation →
UPLOAD → PDF RESPONSE C#
using Aspose.Slides;
using Aspose.Slides.Export;

var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();

app.MapPost("/convert", async (IFormFile file) =>
{
    await using var upload = file.OpenReadStream();
    using var presentation = new Presentation(upload);

    var pdf = new MemoryStream();
    presentation.Save(pdf, SaveFormat.Pdf);
    pdf.Position = 0;

    return Results.File(pdf, "application/pdf", "converted.pdf");
}).DisableAntiforgery();

app.Run();
Minimal API on .NET 8, where an IFormFile endpoint is antiforgery-validated unless you opt out. DisableAntiforgery is safe on an unauthenticated or bearer-token endpoint, not on a cookie-authenticated one. One Presentation instance per request, never shared across threads. Documentation →
EMBEDDED LIC → FULL API C#
using System.IO;
using System.Reflection;
using Aspose.Slides;

// Once per process, before the first Presentation is constructed.
using Stream licenseStream = Assembly
    .GetExecutingAssembly()
    .GetManifestResourceStream("MyApp.Aspose.Slides.NET.lic");

var license = new License();
license.SetLicense(licenseStream);
Without it an evaluation watermark is inserted on open and on save, and text extraction returns one slide only. Documentation →

What goes in, what comes out

Read in only

Other content read inplaced into a presentation rather than opened as one

  • HTML
  • PDF
  • raster image

Read onlyno writer in the API

  • PPT95

Aspose.Slides

12 formats read and written — presentation files, proven by writing each one and reading it back.

  • FODP
  • ODP
  • OTP
  • POT
  • POTM
  • POTX
  • PPS
  • PPSM
  • PPSX
  • PPT
  • PPTM
  • PPTX

Written out only

Written onlyexport targets, not presentation files

  • GIF
  • HTML
  • HTML5
  • MD
  • PDF
  • SWF
  • TIFF
  • XML
  • XPS

Slide imagesrendered from a slide

  • BMP
  • EMF
  • GIF
  • JPEG
  • PNG
  • SVG
  • TIFF
Read from the shipping package on 2026-08-21 by writing each file out and reading it back in.

Capabilities, one line each

This is the .NET build’s capability list, unchanged, because .NET Core loads the same assembly. Two lines need a runtime qualifier rather than a product one: printing goes through System.Drawing printer settings and is Windows-only under .NET Core, and rendering fidelity depends on the fonts present in the image. Where a grey note follows, the capability is delivered through a separate product or comes with a stated limit.

As of 2026-08-18. 49 presentation SDKs and services surveyed. Next re-test: November 2026.

File formats
  • Reads OOXML presentations
  • Writes .pptx
  • Reads legacy binary PowerPoint
  • Writes legacy binary .ppt
  • Reads OpenDocument presentations
  • Writes .odp
  • Exports to PDF
  • Imports PDF into a presentation
  • Exports slides to raster images
  • Exports to HTML
  • Extracts text / Markdown / JSON
Deployment
  • Runs entirely on the customer's own infrastructure
  • Offered as a hosted API the customer calls — through Aspose.Slides Cloud, a separate product
  • Runs without a Microsoft Office / LibreOffice installation
  • Works with no outbound network access
Document operations
  • Create from nothing
  • Open, modify, save back
  • Preserve untouched content
  • Merge or append presentations
  • Slide thumbnails
  • Create charts
Non-functional
  • Published performance numbers — one published capacity figure, no benchmark suite
  • Air-gapped install and licensing
API & language reach
  • .NET · Java / JVM · Python · C / C++
  • JavaScript / TypeScript / Node · PHP
  • Android, SharePoint and JasperReports integrations
  • Language-agnostic REST/HTTP API — through Aspose.Slides Cloud, a separate product
Ecosystem & support
  • Public API reference and guides
  • Runnable sample projects
  • Paid support and escalation

Runs where your code already runs

Where a build of this library is supported, and what each target is for.

  • .NET Core and .NET 5

    Both resolve the netstandard2.0 asset — the net6.0 asset needs .NET 6 or later. That asset declares System.Drawing.Common 5.0.3, so on non-Windows it needs libgdiplus like the net6.0 asset does. Aspose names .NET Core with no minimum version, so there is no vendor-stated floor to quote. The System.Drawing.EnableUnixSupport switch arrived with System.Drawing.Common 6.0 and is neither present nor needed here.

    WINDOWS · LINUX · MACOS

  • .NET 6, 7, 8 and 9

    Binds to the net6.0 asset, which brings System.Drawing.Common 6.0.0 with it. Where new work should start. Aspose's supported-versions list ends at .NET 9 and does not name .NET 10, so confirm with Aspose before targeting it.

    WINDOWS · LINUX · MACOS

  • Linux containers

    The standard build wants libgdiplus. Alpine images also need a font package such as ttf-dejavu, or rendering fails on a missing font.

    DOCKER · KUBERNETES

  • ASP.NET Core

    Read the request stream, write the response stream, no temp files. One Presentation instance per request and never shared between threads.

    KESTREL · IIS · AZURE

  • Aspose.Slides.NET6.CrossPlatform

    Optional sibling package, net6.0 and later, with Aspose's own graphics engine and no System.Drawing.Common dependency. It needs glibc — 2.23 or later on x64, 2.39 or later on ARM64 — so musl images such as Alpine, and CentOS 7, stay on the standard build.

    LINUX · MACOS · WINDOWS

The same package also targets .NET Framework 4.6.2 for Windows-only work. Same object model on other platforms: Java, Python, C++, Node.js, Android, PHP, SharePoint and JasperReports.All high-code APIs →

Start with the trial, license when you ship

The trial is the full API. It applies an evaluation watermark when a presentation is opened or saved and caps text extraction at one slide, so you can test the formats you actually care about before you talk to anyone. A temporary licence lifts both for 30 days.

If you don't want a library

Aspose.Slides Cloud is a hosted REST API for loading, creating, editing and converting presentations.

In use

The product worked as advertised, the documentation was easy to follow, and the support forums were all the help we needed. The final solution that we deployed has exceeded our initial expectations by a great deal.

— BRUCE BRIEN · STRATASCOPE INC, USA

ASPOSE.SLIDES FOR .NET CORE · PRODUCTS.ASPOSE.COMPRESENTATION AUTOMATION WITHOUT MICROSOFT OFFICE