canvas vs gm vs jimp vs sharp
Node.js 图像处理与生成核心方案选型
canvasgmjimpsharp类似的npm包:

Node.js 图像处理与生成核心方案选型

canvasgmjimpsharp 是 Node.js 生态中处理图像的四类主要工具,各自解决了不同的工程痛点。sharp 基于 libvips,主打高性能图像转换(缩放、裁剪、格式互转),是现代后端处理的首选;canvas 基于 Cairo,提供了类似浏览器 Canvas 的 API,擅长动态绘图、文本渲染及图表生成;jimp 是纯 JavaScript 实现,零原生依赖,适合无法安装二进制模块的受限环境;gm 则是 GraphicsMagick 或 ImageMagick 的老牌封装,功能强大但依赖系统二进制文件,常用于维护旧有架构。

npm下载趋势

3 年

GitHub Stars 排名

统计详情

npm包名称
下载量
Stars
大小
Issues
发布时间
License
canvas010,671403 kB4772 个月前MIT
gm06,980121 kB3681 年前MIT
jimp014,6123.31 MB1782 个月前MIT
sharp032,315534 kB1247 个月前Apache-2.0

Node.js 图像处理与生成:Sharp vs Canvas vs Jimp vs GM

在 Node.js 后端开发中,处理图片是常见需求 —— 无论是压缩用户上传的头像、生成动态海报,还是批量转换格式。canvasgmjimpsharp 代表了四种不同的技术路线。本文将从依赖环境、性能表现、API 设计及适用场景四个维度进行深度对比,帮助你做出架构决策。

📦 依赖与安装:原生绑定 vs 纯 JS

部署的难易程度往往决定了运维的成本。这四个包在底层依赖上有本质区别。

sharp 基于 C++ 编写的 libvips 库。它通过 npm 分发预编译的二进制文件,大多数情况下无需手动配置环境。

# sharp: 通常直接安装即可,npm 会自动下载对应平台的二进制包
npm install sharp

canvas 基于 Cairo 图形库。在 macOS 和 Windows 上通常有预编译包,但在 Linux 服务器上可能需要安装系统级依赖(如 libcairo2-dev)。

# canvas: Linux 下可能需要先安装系统依赖
sudo apt-get install -y libcairo2-dev libjpeg-dev libpango1.0-dev libgif-dev
npm install canvas

jimp 是纯 JavaScript 实现,没有任何原生依赖。这是它最大的优势,安装极其简单,兼容性最好。

# jimp: 纯 JS,无系统依赖
npm install jimp

gm 是 GraphicsMagick 或 ImageMagick 的命令行工具封装。你必须在操作系统层面预先安装这些软件,否则无法运行。

# gm: 必须先安装系统软件
sudo apt-get install graphicsmagick
npm install gm

💡 架构建议:在容器化(Docker)部署中,sharpjimp 最省心。canvasgm 会增加 Docker 镜像的构建复杂度和体积。

⚡ 性能表现:处理速度与内存占用

图像处理是 CPU 密集型任务,性能差异在高并发下会被放大。

sharp 是性能王者。libvips 针对流式处理和内存管理做了极致优化,处理大图时内存占用远低于其他库。

// sharp: 流式处理,内存效率极高
const sharp = require('sharp');
sharp('input.jpg')
  .resize(800, 600)
  .toFile('output.jpg')
  .then(() => console.log('Done'));

canvas 性能中等。它需要将图片加载到内存中的位图对象进行绘制,适合中等规模的图像合成。

// canvas: 加载到内存上下文
const { createCanvas, loadImage } = require('canvas');
async function draw() {
  const canvas = createCanvas(800, 600);
  const ctx = canvas.getContext('2d');
  const img = await loadImage('input.jpg');
  ctx.drawImage(img, 0, 0);
  // ... 绘图操作
}

jimp 性能较弱。由于是纯 JS 解码和编码,处理高清图片时速度明显慢于原生库,且内存占用较高。

// jimp: 纯 JS 处理,大文件较慢
const Jimp = require('jimp');
Jimp.read('input.jpg').then(image => {
  image.resize(800, 600);
  image.write('output.jpg');
});

gm 性能取决于底层 ImageMagick 配置。虽然底层是 C 语言,但通过子进程调用命令行工具带来了额外的进程开销。

// gm: 调用外部进程
const gm = require('gm');
gm('input.jpg')
  .resize(800, 600)
  .write('output.jpg', (err) => {
    if (!err) console.log('Done');
  });

🎨 核心能力:绘图 vs 转换

这是选择 canvas 与其他三个包的分水岭。sharpjimpgm 主要侧重于图像转换(Transform),而 canvas 侧重于图像绘制(Drawing)。

1. 文本渲染与复杂合成

如果你需要在图片上写文字、画圆、画线,canvas 是唯一原生支持良好的选择。

// canvas: 强大的 2D 上下文 API
ctx.font = '30px Arial';
ctx.fillText('Hello World', 10, 50);
ctx.beginPath();
ctx.arc(100, 100, 50, 0, 2 * Math.PI);
ctx.stroke();

其他库处理文本通常比较麻烦,需要指定字体路径,且不支持矢量绘图。

// jimp: 文本支持有限,需加载字体文件
Jimp.loadFont(Jimp.FONT_SANS_32_BLACK).then(font => {
  image.print(font, 10, 10, 'Hello World');
});

// sharp: 文本支持较新,功能不如 canvas 灵活
sharp({
  text: {
    text: 'Hello World',
    font: 'Arial',
    dpi: 300
  }
})
.toFile('text.png');

2. 格式转换与压缩

在调整尺寸、转换 WebP/AVIF 格式方面,sharp 表现最好,支持现代格式且压缩率高。

// sharp: 轻松转换为现代格式
sharp('input.png').webp({ quality: 80 }).toFile('output.webp');

// jimp: 支持格式较少,主要传统格式
image.write('output.jpg'); 

// gm: 支持格式多,但配置复杂
gm('input.png').write('output.webp', callback);

🛠️ 实际场景选型指南

场景 A:电商商品图批量处理

需求:用户上传 5MB 原图,后端需生成缩略图、水印图,并转换为 WebP。 ✅ 推荐sharp 理由:性能至关重要。sharp 能在几百毫秒内完成处理,且内存占用低,不会阻塞事件循环。

场景 B:生成每日运势海报

需求:根据用户数据,在背景图上动态绘制文字、星座图标、二维码。 ✅ 推荐canvas 理由:需要复杂的绘图 API(文本换行、颜色填充、路径绘制)。sharp 做这些非常痛苦,而 canvas 是前端开发者的舒适区。

场景 C:Serverless 函数处理

需求:在 AWS Lambda 或 Vercel Functions 中简单调整图片尺寸。 ✅ 推荐sharp (首选) 或 jimp (备选) 理由sharp 有针对 Serverless 的优化层。但如果遇到兼容性问题(如某些边缘节点不支持原生模块),jimp 是可靠的纯 JS 兜底方案。

场景 D:维护 5 年前的老系统

需求:系统已经依赖 ImageMagick 进行复杂的滤镜处理。 ✅ 推荐gm 理由:重构成本过高。gm 能直接复用现有的 ImageMagick 能力,但建议规划迁移至 sharp

📊 综合对比总结

特性sharpcanvasjimpgm
底层核心libvips (C++)Cairo (C++)Pure JavaScriptImageMagick (CLI)
安装难度⭐ 简单 (预编译)⭐⭐ 中等 (Linux 需依赖)⭐ 极简 (无依赖)⭐⭐⭐ 困难 (需系统软件)
处理性能🚀 极快⚡ 中等🐢 较慢⚡ 快 (但有进程开销)
绘图能力弱 (仅基础文本)🎨 极强 (完整 2D API)弱 (基础文本)中 (命令行参数)
内存占用低 (流式)中 (位图)高 (全量加载)中 (外部进程)
适用场景图片压缩、转换、水印海报生成、图表、绘图简单处理、无原生环境旧系统维护、特殊滤镜

💡 架构师建议

在现代 Node.js 架构中,sharp 应作为图像处理的首选默认方案。它在性能、维护性和功能之间取得了最佳平衡。绝大多数“调整大小”、“裁剪”、“格式转换”的需求,sharp 都能以最低的成本解决。

canvas 是特定的补充工具。当你的业务涉及“生成图片”(如社交分享图、数据可视化截图)而非单纯“处理图片”时,引入 canvas 是合理的。不要试图用 sharp 去画复杂的文字,也不要用 canvas 去批量压缩成千上万张图片。

jimpgm 逐渐边缘化。除非你有明确的“无原生依赖”或“遗留系统兼容”需求,否则在新项目中应避免使用它们。技术选型的本质是降低长期维护成本,选择社区活跃、性能优越的工具(如 sharp)能让你的团队走得更远。

如何选择: canvas vs gm vs jimp vs sharp

  • canvas:

    选择 canvas 如果你需要在服务端动态绘制图表、在图片上渲染复杂文本、或进行像素级的绘图操作。它的 API 与浏览器 Canvas 一致,适合前端开发者无缝迁移绘图逻辑。

  • gm:

    选择 gm 仅当你维护依赖 ImageMagick 的旧系统,或需要使用某些 sharp 尚未支持的特定图像处理算法。新项目通常不建议使用,因为配置系统依赖较为繁琐且性能不如 sharp

  • jimp:

    选择 jimp 如果你的运行环境无法安装原生模块(如某些 Serverless 函数、纯 JS 沙箱),或者你需要一套代码同时运行在 Node.js 和浏览器中。注意它在处理大图时性能较低。

  • sharp:

    选择 sharp 如果你的项目需要高性能的图像缩放、裁剪、格式转换或水印处理。它是目前生产环境的标准选择,安装简单(预编译二进制),处理速度极快,适合高并发场景。

canvas的README

node-canvas

Test NPM version

node-canvas is a Cairo-backed Canvas implementation for Node.js.

Installation

$ npm install canvas

By default, pre-built binaries will be downloaded if you're on one of the following platforms:

  • macOS x86/64
  • macOS aarch64 (aka Apple silicon)
  • Linux x86/64 (glibc only)
  • Windows x86/64

If you want to build from source, use npm install --build-from-source and see the Compiling section below.

The minimum version of Node.js required is 18.12.0.

Compiling

If you don't have a supported OS or processor architecture, or you use --build-from-source, the module will be compiled on your system. This requires several dependencies, including Cairo and Pango.

For detailed installation information, see the wiki. One-line installation instructions for common OSes are below. Note that libgif/giflib, librsvg and libjpeg are optional and only required if you need GIF, SVG and JPEG support, respectively. Cairo v1.10.0 or later is required.

OSCommand
macOSUsing Homebrew:
brew install pkg-config cairo pango libpng jpeg giflib librsvg pixman python-setuptools
Ubuntusudo apt-get install build-essential libcairo2-dev libpango1.0-dev libjpeg-dev libgif-dev librsvg2-dev
Fedorasudo yum install gcc-c++ cairo-devel pango-devel libjpeg-turbo-devel giflib-devel
Solarispkgin install cairo pango pkg-config xproto renderproto kbproto xextproto
OpenBSDdoas pkg_add cairo pango png jpeg giflib
WindowsSee the wiki
OthersSee the wiki

Mac OS X v10.11+: If you have recently updated to Mac OS X v10.11+ and are experiencing trouble when compiling, run the following command: xcode-select --install. Read more about the problem on Stack Overflow. If you have xcode 10.0 or higher installed, in order to build from source you need NPM 6.4.1 or higher.

Quick Example

const { createCanvas, loadImage } = require('canvas')
const canvas = createCanvas(200, 200)
const ctx = canvas.getContext('2d')

// Write "Awesome!"
ctx.font = '30px Impact'
ctx.rotate(0.1)
ctx.fillText('Awesome!', 50, 100)

// Draw line under text
var text = ctx.measureText('Awesome!')
ctx.strokeStyle = 'rgba(0,0,0,0.5)'
ctx.beginPath()
ctx.lineTo(50, 102)
ctx.lineTo(50 + text.width, 102)
ctx.stroke()

// Draw cat with lime helmet
loadImage('examples/images/lime-cat.jpg').then((image) => {
  ctx.drawImage(image, 50, 0, 70, 70)

  console.log('<img src="https://raw.githubusercontent.com/Automattic/node-canvas/HEAD/' + canvas.toDataURL() + '" />')
})

Upgrading from 1.x to 2.x

See the changelog for a guide to upgrading from 1.x to 2.x.

For version 1.x documentation, see the v1.x branch.

Documentation

This project is an implementation of the Web Canvas API and implements that API as closely as possible. For API documentation, please visit Mozilla Web Canvas API. (See Compatibility Status for the current API compliance.) All utility methods and non-standard APIs are documented below.

Utility methods

Non-standard APIs

createCanvas()

createCanvas(width: number, height: number, type?: 'PDF'|'SVG') => Canvas

Creates a Canvas instance. This method works in both Node.js and Web browsers, where there is no Canvas constructor. (See browser.js for the implementation that runs in browsers.)

const { createCanvas } = require('canvas')
const mycanvas = createCanvas(200, 200)
const myPDFcanvas = createCanvas(600, 800, 'pdf') // see "PDF Support" section

createImageData()

createImageData(width: number, height: number) => ImageData
createImageData(data: Uint8ClampedArray, width: number, height?: number) => ImageData
// for alternative pixel formats:
createImageData(data: Uint16Array, width: number, height?: number) => ImageData

Creates an ImageData instance. This method works in both Node.js and Web browsers.

const { createImageData } = require('canvas')
const width = 20, height = 20
const arraySize = width * height * 4
const mydata = createImageData(new Uint8ClampedArray(arraySize), width)

loadImage()

loadImage() => Promise<Image>

Convenience method for loading images. This method works in both Node.js and Web browsers.

const { loadImage } = require('canvas')
const myimg = loadImage('http://server.com/image.png')

myimg.then(() => {
  // do something with image
}).catch(err => {
  console.log('oh no!', err)
})

// or with async/await:
const myimg = await loadImage('http://server.com/image.png')
// do something with image

registerFont()

registerFont(path: string, { family: string, weight?: string, style?: string }) => void

To use a font file that is not installed as a system font, use registerFont() to register the font with Canvas.

const { registerFont, createCanvas } = require('canvas')
registerFont('comicsans.ttf', { family: 'Comic Sans' })

const canvas = createCanvas(500, 500)
const ctx = canvas.getContext('2d')

ctx.font = '12px "Comic Sans"'
ctx.fillText('Everyone hates this font :(', 250, 10)

The second argument is an object with properties that resemble the CSS properties that are specified in @font-face rules. You must specify at least family. weight, and style are optional and default to 'normal'.

deregisterAllFonts()

deregisterAllFonts() => void

Use deregisterAllFonts to unregister all fonts that have been previously registered. This method is useful when you want to remove all registered fonts, such as when using the canvas in tests

const { registerFont, createCanvas, deregisterAllFonts } = require('canvas')

describe('text rendering', () => {
    afterEach(() => {
        deregisterAllFonts();
    })
    it('should render text with Comic Sans', () => {
        registerFont('comicsans.ttf', { family: 'Comic Sans' })

        const canvas = createCanvas(500, 500)
        const ctx = canvas.getContext('2d')
        
        ctx.font = '12px "Comic Sans"'
        ctx.fillText('Everyone loves this font :)', 250, 10)
        
        // assertScreenshot()
    })
})

Image#src

img.src: string|Buffer

As in browsers, img.src can be set to a data: URI or a remote URL. In addition, node-canvas allows setting src to a local file path or Buffer instance.

const { Image } = require('canvas')

// From a buffer:
fs.readFile('images/squid.png', (err, squid) => {
  if (err) throw err
  const img = new Image()
  img.onload = () => ctx.drawImage(img, 0, 0)
  img.onerror = err => { throw err }
  img.src = squid
})

// From a local file path:
const img = new Image()
img.onload = () => ctx.drawImage(img, 0, 0)
img.onerror = err => { throw err }
img.src = 'images/squid.png'

// From a remote URL:
img.src = 'http://picsum.photos/200/300'
// ... as above

// From a `data:` URI:
img.src = 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAUAAAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/w38GIAXDIBKE0DHxgljNBAAO9TXL0Y4OHwAAAABJRU5ErkJggg=='
// ... as above

Note: In some cases, img.src= is currently synchronous. However, you should always use img.onload and img.onerror, as we intend to make img.src= always asynchronous as it is in browsers. See https://github.com/Automattic/node-canvas/issues/1007.

Image#dataMode

img.dataMode: number

Applies to JPEG images drawn to PDF canvases only.

Setting img.dataMode = Image.MODE_MIME or Image.MODE_MIME|Image.MODE_IMAGE enables MIME data tracking of images. When MIME data is tracked, PDF canvases can embed JPEGs directly into the output, rather than re-encoding into PNG. This can drastically reduce filesize and speed up rendering.

const { Image, createCanvas } = require('canvas')
const canvas = createCanvas(w, h, 'pdf')
const img = new Image()
img.dataMode = Image.MODE_IMAGE // Only image data tracked
img.dataMode = Image.MODE_MIME // Only mime data tracked
img.dataMode = Image.MODE_MIME | Image.MODE_IMAGE // Both are tracked

If working with a non-PDF canvas, image data must be tracked; otherwise the output will be junk.

Enabling mime data tracking has no benefits (only a slow down) unless you are generating a PDF.

Canvas#toBuffer()

canvas.toBuffer((err: Error|null, result: Buffer) => void, mimeType?: string, config?: any) => void
canvas.toBuffer(mimeType?: string, config?: any) => Buffer

Creates a Buffer object representing the image contained in the canvas.

  • callback If provided, the buffer will be provided in the callback instead of being returned by the function. Invoked with an error as the first argument if encoding failed, or the resulting buffer as the second argument if it succeeded. Not supported for mimeType raw or for PDF or SVG canvases.
  • mimeType A string indicating the image format. Valid options are image/png, image/jpeg (if node-canvas was built with JPEG support), raw (unencoded data in BGRA order on little-endian (most) systems, ARGB on big-endian systems; top-to-bottom), application/pdf (for PDF canvases) and image/svg+xml (for SVG canvases). Defaults to image/png for image canvases, or the corresponding type for PDF or SVG canvas.
  • config
    • For image/jpeg, an object specifying the quality (0 to 1), if progressive compression should be used and/or if chroma subsampling should be used: {quality: 0.75, progressive: false, chromaSubsampling: true}. All properties are optional.

    • For image/png, an object specifying the ZLIB compression level (between 0 and 9), the compression filter(s), the palette (indexed PNGs only), the the background palette index (indexed PNGs only) and/or the resolution (ppi): {compressionLevel: 6, filters: canvas.PNG_ALL_FILTERS, palette: undefined, backgroundIndex: 0, resolution: undefined}. All properties are optional.

      Note that the PNG format encodes the resolution in pixels per meter, so if you specify 96, the file will encode 3780 ppm (~96.01 ppi). The resolution is undefined by default to match common browser behavior.

    • For application/pdf, an object specifying optional document metadata: {title: string, author: string, subject: string, keywords: string, creator: string, creationDate: Date, modDate: Date}. All properties are optional and default to undefined, except for creationDate, which defaults to the current date. Adding metadata requires Cairo 1.16.0 or later.

      For a description of these properties, see page 550 of PDF 32000-1:2008.

      Note that there is no standard separator for keywords. A space is recommended because it is in common use by other applications, and Cairo will enclose the list of keywords in quotes if a comma or semicolon is used.

Return value

If no callback is provided, a Buffer. If a callback is provided, none.

Examples

// Default: buf contains a PNG-encoded image
const buf = canvas.toBuffer()

// PNG-encoded, zlib compression level 3 for faster compression but bigger files, no filtering
const buf2 = canvas.toBuffer('image/png', { compressionLevel: 3, filters: canvas.PNG_FILTER_NONE })

// JPEG-encoded, 50% quality
const buf3 = canvas.toBuffer('image/jpeg', { quality: 0.5 })

// Asynchronous PNG
canvas.toBuffer((err, buf) => {
  if (err) throw err // encoding failed
  // buf is PNG-encoded image
})

canvas.toBuffer((err, buf) => {
  if (err) throw err // encoding failed
  // buf is JPEG-encoded image at 95% quality
}, 'image/jpeg', { quality: 0.95 })

// BGRA pixel values, native-endian
const buf4 = canvas.toBuffer('raw')
const { stride, width } = canvas
// In memory, this is `canvas.height * canvas.stride` bytes long.
// The top row of pixels, in BGRA order on little-endian hardware,
// left-to-right, is:
const topPixelsBGRALeftToRight = buf4.slice(0, width * 4)
// And the third row is:
const row3 = buf4.slice(2 * stride, 2 * stride + width * 4)

// SVG and PDF canvases
const myCanvas = createCanvas(w, h, 'pdf')
myCanvas.toBuffer() // returns a buffer containing a PDF-encoded canvas
// With optional metadata:
myCanvas.toBuffer('application/pdf', {
  title: 'my picture',
  keywords: 'node.js demo cairo',
  creationDate: new Date()
})

Canvas#createPNGStream()

canvas.createPNGStream(config?: any) => ReadableStream

Creates a ReadableStream that emits PNG-encoded data.

  • config An object specifying the ZLIB compression level (between 0 and 9), the compression filter(s), the palette (indexed PNGs only) and/or the background palette index (indexed PNGs only): {compressionLevel: 6, filters: canvas.PNG_ALL_FILTERS, palette: undefined, backgroundIndex: 0, resolution: undefined}. All properties are optional.

Examples

const fs = require('fs')
const out = fs.createWriteStream(__dirname + '/test.png')
const stream = canvas.createPNGStream()
stream.pipe(out)
out.on('finish', () =>  console.log('The PNG file was created.'))

To encode indexed PNGs from canvases with pixelFormat: 'A8' or 'A1', provide an options object:

const palette = new Uint8ClampedArray([
  //r    g    b    a
    0,  50,  50, 255, // index 1
   10,  90,  90, 255, // index 2
  127, 127, 255, 255
  // ...
])
canvas.createPNGStream({
  palette: palette,
  backgroundIndex: 0 // optional, defaults to 0
})

Canvas#createJPEGStream()

canvas.createJPEGStream(config?: any) => ReadableStream

Creates a ReadableStream that emits JPEG-encoded data.

Note: At the moment, createJPEGStream() is synchronous under the hood. That is, it runs in the main thread, not in the libuv threadpool.

  • config an object specifying the quality (0 to 1), if progressive compression should be used and/or if chroma subsampling should be used: {quality: 0.75, progressive: false, chromaSubsampling: true}. All properties are optional.

Examples

const fs = require('fs')
const out = fs.createWriteStream(__dirname + '/test.jpeg')
const stream = canvas.createJPEGStream()
stream.pipe(out)
out.on('finish', () =>  console.log('The JPEG file was created.'))

// Disable 2x2 chromaSubsampling for deeper colors and use a higher quality
const stream = canvas.createJPEGStream({
  quality: 0.95,
  chromaSubsampling: false
})

Canvas#createPDFStream()

canvas.createPDFStream(config?: any) => ReadableStream
  • config an object specifying optional document metadata: {title: string, author: string, subject: string, keywords: string, creator: string, creationDate: Date, modDate: Date}. See toBuffer() for more information. Adding metadata requires Cairo 1.16.0 or later.

Applies to PDF canvases only. Creates a ReadableStream that emits the encoded PDF. canvas.toBuffer() also produces an encoded PDF, but createPDFStream() can be used to reduce memory usage.

Canvas#toDataURL()

This is a standard API, but several non-standard calls are supported. The full list of supported calls is:

dataUrl = canvas.toDataURL() // defaults to PNG
dataUrl = canvas.toDataURL('image/png')
dataUrl = canvas.toDataURL('image/jpeg')
dataUrl = canvas.toDataURL('image/jpeg', quality) // quality from 0 to 1
canvas.toDataURL((err, png) => { }) // defaults to PNG
canvas.toDataURL('image/png', (err, png) => { })
canvas.toDataURL('image/jpeg', (err, jpeg) => { }) // sync JPEG is not supported
canvas.toDataURL('image/jpeg', {...opts}, (err, jpeg) => { }) // see Canvas#createJPEGStream for valid options
canvas.toDataURL('image/jpeg', quality, (err, jpeg) => { }) // spec-following; quality from 0 to 1

CanvasRenderingContext2D#patternQuality

context.patternQuality: 'fast'|'good'|'best'|'nearest'|'bilinear'

Defaults to 'good'. Affects pattern (gradient, image, etc.) rendering quality.

CanvasRenderingContext2D#quality

context.quality: 'fast'|'good'|'best'|'nearest'|'bilinear'

Defaults to 'good'. Like patternQuality, but applies to transformations affecting more than just patterns.

CanvasRenderingContext2D#textDrawingMode

context.textDrawingMode: 'path'|'glyph'

Defaults to 'path'. The effect depends on the canvas type:

  • Standard (image) glyph and path both result in rasterized text. Glyph mode is faster than path, but may result in lower-quality text, especially when rotated or translated.

  • PDF glyph will embed text instead of paths into the PDF. This is faster to encode, faster to open with PDF viewers, yields a smaller file size and makes the text selectable. The subset of the font needed to render the glyphs will be embedded in the PDF. This is usually the mode you want to use with PDF canvases.

  • SVG glyph does not cause <text> elements to be produced as one might expect (cairo bug). Rather, glyph will create a <defs> section with a <symbol> for each glyph, then those glyphs be reused via <use> elements. path mode creates a <path> element for each text string. glyph mode is faster and yields a smaller file size.

In glyph mode, ctx.strokeText() and ctx.fillText() behave the same (aside from using the stroke and fill style, respectively).

This property is tracked as part of the canvas state in save/restore.

CanvasRenderingContext2D#globalCompositeOperation = 'saturate'

In addition to all of the standard global composite operations defined by the Canvas specification, the 'saturate' operation is also available.

CanvasRenderingContext2D#antialias

context.antialias: 'default'|'none'|'gray'|'subpixel'

Sets the anti-aliasing mode.

PDF Output Support

node-canvas can create PDF documents instead of images. The canvas type must be set when creating the canvas as follows:

const canvas = createCanvas(200, 500, 'pdf')

An additional method .addPage() is then available to create multiple page PDFs:

// On first page
ctx.font = '22px Helvetica'
ctx.fillText('Hello World', 50, 80)

ctx.addPage()
// Now on second page
ctx.font = '22px Helvetica'
ctx.fillText('Hello World 2', 50, 80)

canvas.toBuffer() // returns a PDF file
canvas.createPDFStream() // returns a ReadableStream that emits a PDF
// With optional document metadata (requires Cairo 1.16.0):
canvas.toBuffer('application/pdf', {
  title: 'my picture',
  keywords: 'node.js demo cairo',
  creationDate: new Date()
})

It is also possible to create pages with different sizes by passing width and height to the .addPage() method:

ctx.font = '22px Helvetica'
ctx.fillText('Hello World', 50, 80)
ctx.addPage(400, 800)

ctx.fillText('Hello World 2', 50, 80)

It is possible to add hyperlinks using .beginTag() and .endTag():

ctx.beginTag('Link', "uri='https://google.com'")
ctx.font = '22px Helvetica'
ctx.fillText('Hello World', 50, 80)
ctx.endTag('Link')

Or with a defined rectangle:

ctx.beginTag('Link', "uri='https://google.com' rect=[50 80 100 20]")
ctx.endTag('Link')

Note that the syntax for attributes is unique to Cairo. See cairo_tag_begin for the full documentation.

You can create areas on the canvas using the "cairo.dest" tag, and then link to them using the "Link" tag with the dest= attribute. You can also define PDF structure for accessibility by using tag names like "P", "H1", and "TABLE". The standard tags are defined in §14.8.4 of the PDF 1.7 specification.

See also:

SVG Output Support

node-canvas can create SVG documents instead of images. The canvas type must be set when creating the canvas as follows:

const canvas = createCanvas(200, 500, 'svg')
// Use the normal primitives.
fs.writeFileSync('out.svg', canvas.toBuffer())

SVG Image Support

If librsvg is available when node-canvas is installed, node-canvas can render SVG images to your canvas context. This currently works by rasterizing the SVG image (i.e. drawing an SVG image to an SVG canvas will not preserve the SVG data).

const img = new Image()
img.onload = () => ctx.drawImage(img, 0, 0)
img.onerror = err => { throw err }
img.src = './example.svg'

Image pixel formats (experimental)

node-canvas has experimental support for additional pixel formats, roughly following the Canvas color space proposal.

const canvas = createCanvas(200, 200)
const ctx = canvas.getContext('2d', { pixelFormat: 'A8' })

By default, canvases are created in the RGBA32 format, which corresponds to the native HTML Canvas behavior. Each pixel is 32 bits. The JavaScript APIs that involve pixel data (getImageData, putImageData) store the colors in the order {red, green, blue, alpha} without alpha pre-multiplication. (The C++ API stores the colors in the order {alpha, red, green, blue} in native-endian ordering, with alpha pre-multiplication.)

These additional pixel formats have experimental support:

  • RGB24 Like RGBA32, but the 8 alpha bits are always opaque. This format is always used if the alpha context attribute is set to false (i.e. canvas.getContext('2d', {alpha: false})). This format can be faster than RGBA32 because transparency does not need to be calculated.
  • A8 Each pixel is 8 bits. This format can either be used for creating grayscale images (treating each byte as an alpha value), or for creating indexed PNGs (treating each byte as a palette index) (see the example using alpha values with fillStyle and the example using imageData).
  • RGB16_565 Each pixel is 16 bits, with red in the upper 5 bits, green in the middle 6 bits, and blue in the lower 5 bits, in native platform endianness. Some hardware devices and frame buffers use this format. Note that PNG does not support this format; when creating a PNG, the image will be converted to 24-bit RGB. This format is thus suboptimal for generating PNGs. ImageData instances for this mode use a Uint16Array instead of a Uint8ClampedArray.
  • A1 Each pixel is 1 bit, and pixels are packed together into 32-bit quantities. The ordering of the bits matches the endianness of the platform: on a little-endian machine, the first pixel is the least-significant bit. This format can be used for creating single-color images. Support for this format is incomplete, see note below.
  • RGB30 Each pixel is 30 bits, with red in the upper 10, green in the middle 10, and blue in the lower 10. (Requires Cairo 1.12 or later.) Support for this format is incomplete, see note below.

Notes and caveats:

  • Using a non-default format can affect the behavior of APIs that involve pixel data:

    • context2d.createImageData The size of the array returned depends on the number of bit per pixel for the underlying image data format, per the above descriptions.
    • context2d.getImageData The format of the array returned depends on the underlying image mode, per the above descriptions. Be aware of platform endianness, which can be determined using node.js's os.endianness() function.
    • context2d.putImageData As above.
  • A1 and RGB30 do not yet support getImageData or putImageData. Have a use case and/or opinion on working with these formats? Open an issue and let us know! (See #935.)

  • A1, A8, RGB30 and RGB16_565 with shadow blurs may crash or not render properly.

  • The ImageData(width, height) and ImageData(Uint8ClampedArray, width) constructors assume 4 bytes per pixel. To create an ImageData instance with a different number of bytes per pixel, use new ImageData(new Uint8ClampedArray(size), width, height) or new ImageData(new Uint16ClampedArray(size), width, height).

Testing

First make sure you've built the latest version. Get all the deps you need (see compiling above), and run:

npm install --build-from-source

For visual tests: npm run test-server and point your browser to http://localhost:4000.

For unit tests: npm run test.

Benchmarks

Benchmarks live in the benchmarks directory.

Examples

Examples line in the examples directory. Most produce a png image of the same name, and others such as live-clock.js launch an HTTP server to be viewed in the browser.

Original Authors

License

node-canvas

(The MIT License)

Copyright (c) 2010 LearnBoost, and contributors <dev@learnboost.com>

Copyright (c) 2014 Automattic, Inc and contributors <dev@automattic.com>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

BMP parser

See license