anchor.diff:  (**
   ---
  -title: Basics 
  +title: Static image export
   category: General
   categoryindex: 1
   index: 2
  
positive.code:         Height=300
      )
  
  #if IPYNB
  DisplayExtensions.DisplayAs(svgString,"image/svg+xml")
  #endif // IPYNB
  
  svgString
  (***include-it-raw***)
negative.code: 
  # Static image export
  
  ### Table of contents
  
  - [Saving static images](#Saving-static-images)
  - [Generating URIs for static chart images](#Generating-URIs-for-static-chart-images)
  - [Including static images in dotnet interactive notebooks](#Including-static-images-in-dotnet-interactive-notebooks)
  
  As Plotly.NET generates static html pages that contain charts rendered by plotly.js, static image export needs a lot more overhead under the hood 
  than you might expect. The underlying renderer needs to execute javascript, leading to the usage of headless browsers.
  
  The package `Plotly.NET.ImageExport` contains extensions for Plotly.NET to render static images. It is designed with extensibility in mind and
  it is very easy to add a new rendering engine. The current engines are provided:
  
  | Rendering engine | Type | Prerequisites |
  |-|-|-|
  | [PuppeteerSharp](https://github.com/hardkoded/puppeteer-sharp) | headless browser | [read more here](https://github.com/hardkoded/puppeteer-sharp#prerequisites) |
  
  ## Saving static images
  
  By referencing the `Plotly.NET.ImageExport` package, you get access to:
  
   - jpg via `Chart.SaveJPG`
   - png via `Chart.SavePNG`
   - svg via `Chart.SaveSVG`
  
  (and Extensions for C# style fluent interfaces by opening the `GenericChartExtensions` namespace)
  
  The parameters for all three functions are exactly the same. 
  *)
  