npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@polotno/psd-import

v0.1.0

Published

Convert Photoshop PSD files into editable Polotno JSON designs while preserving text, vector, and raster layers

Readme

@polotno/psd-import — PSD to editable Polotno JSON

Parse a Photoshop .psd file and convert it into a JSON document that matches the Polotno schema. Works in the browser and in Node.

Works without the editor. The converter returns plain Polotno design JSON.

Runtime: Browser and Node.js. Conversion runs locally.

Documentation · Try PSD to JSON in your browser

License: Non-production use is free, with no time limit. Production use requires a valid Polotno subscription. Read the license.

Install

npm install @polotno/psd-import

Usage

psdToJson accepts an ArrayBuffer or Uint8Array of PSD bytes and returns a Polotno-schema JSON document.

Browser — read bytes from a file input:

import { psdToJson } from '@polotno/psd-import';

const file = input.files[0];
const buffer = await file.arrayBuffer();
const json = await psdToJson({ psd: buffer });

// Optional: load into a Polotno store
store.loadJSON(json);

Node.js — read bytes from disk:

import { readFile } from 'node:fs/promises';
import { psdToJson } from '@polotno/psd-import';

const buffer = await readFile('./design.psd');
const json = await psdToJson({ psd: buffer });

The returned object matches the Polotno JSON schema: { width, height, fonts, pages, unit, dpi }.

How it works

The goal is to keep as many of the PSD's layers as separate, editable elements as possible, instead of flattening the file into a single image. Each PSD layer is mapped to the closest equivalent in the Polotno schema:

  • Text layers stay as editable text — font family, weight, style, size, color, alignment, line height, and letter spacing carry over.
  • Shape and vector layers become SVG elements with their fills, gradients, and strokes preserved.
  • Raster layers become images. When a layer uses effects the schema can't represent natively (gradient/color overlays, gradient maps, hue/saturation, brightness/contrast, …), the effect is baked into that layer's pixels so it still looks right while every other element remains separate.
  • Masks and group effects are applied to the layers underneath them, so masked content and folder-level overlays render correctly without collapsing the document.
  • Blend modes pass through where the schema supports them; unsupported modes are flattened only with the layers they depend on.

The PSD's pre-rendered composite image is intentionally not used — every element stays selectable and editable.

License

See LICENSE.md.