Multi-framework responsive image component
2.1k
Stars
67
Forks
50
Open issues
30
Contributors
AI Analysis
unpic-img is a cross-framework responsive image component that generates optimized image markup for React, Vue, SolidJS, Svelte, Astro, Preact, Qwik, WebC, Angular, and Lit. It serves developers building performance-focused web applications who need automatic srcset generation, lazy loading, and modern format delivery (WebP, AVIF) without build-time image processing, by leveraging existing image CDN capabilities. It benefits frontend teams across multiple frameworks who prioritize page perfor...
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Multi-framework responsive image component leveraging image CDNs without client JavaScript
unpic-img is a TypeScript component library that generates optimized responsive images across React, Vue, SolidJS, Svelte, Astro, Preact, Qwik, WebC, Angular, and Lit. It works by detecting image CDN capabilities (Cloudinary, Imgix, Shopify, etc.) and generating correct srcset/sizes attributes server-side, producing zero-runtime-overhead HTML. Adoption appears concentrated in Astro and frameworks with strong SSR/SSG workflows; real-world production usage is not extensively documented.
Created February 2023, unpic-img built on the unpic library ecosystem (image CDN detection/URL manipulation). Positioned as a reaction to heavyweight image component patterns in frameworks like Next.js that pre-render images or add wrapper elements; targets developers prioritizing semantic HTML and minimal JavaScript.
Repository gained 2,060 stars over ~3.3 years at a modest pace (~625 stars/year). Last 7 days show +4 stars. Growth appears to have plateaued relative to initial hype; repository remains actively maintained (last push 2026-07-05) but does not show accelerating adoption signals. Steady state suggests niche but functional positioning rather than explosive adoption.
Adoption not verified. README lacks case studies, production testimonials, or documented deployments. No evidence of large-scale usage. The library appears designed for and likely used by teams with existing image CDN infrastructure and multi-framework codebases, but such usage is not publicly claimed or demonstrated.
Likely a monorepo or multi-package structure supporting 10+ framework bindings, built on a shared unpic core for CDN detection. Based on README, the library generates semantic single-`<img>` elements with CSS-only responsive behavior (object-fit, aspect-ratio), avoiding wrapper divs. Appears to use standard framework-specific component patterns (props/slots) per target framework. Implementation strategy around CDN URL APIs suggests relatively stable, non-invasive codebase.
Not documented in README. No mention of test harness, coverage metrics, or test suite structure.
Last push 2026-07-05 (1 day before evaluation date) indicates active maintenance. Repository age (3+ years) and continued updates suggest sustained stewardship. Low weekly star gain (+4 in 7 days) and lack of public issue/PR metadata prevents assessment of velocity or backlog health, but recent activity rules out abandonment.
ADOPT IF: you operate multiple JavaScript frameworks (React, Vue, Svelte, Astro), already use an image CDN (Cloudinary, Imgix, Shopify), prioritize semantic HTML and minimal runtime JavaScript, and want a single component library pattern across projects. AVOID IF: you are Astro-only (use native Astro Image), need image optimization as a service (use Next.js Image or ipx), lack an image CDN, or require extensive built-in placeholder/lazy-loading helpers. MONITOR IF: you are evaluating multi-framework image strategies and want to validate real-world production usage before committing; adoption signals remain modest despite technical soundness.
Independent dimensions
Mainstream potential
4/10
Technical importance
7/10
Adoption evidence
2/10
- Limited documented real-world production usage may indicate adoption barriers (CDN requirement, framework-specific gotchas) not visible in README.
- Multi-framework support increases surface area for bugs and compatibility issues; maintenance burden on a small team could slow updates.
- Dependence on unpic library for CDN detection means changes to unpic or new CDN variants could affect stability.
- Star plateau and low recent growth suggest potential difficulty reaching mainstream adoption; niche positioning may be permanent.
- No public documentation of adoption rate, issue response time, or roadmap visibility; unclear how actively issues are triaged.
unpic-img will likely remain a stable, niche tool for polyglot/multi-framework teams with mature image CDN infrastructure. Growth will plateau unless marketing or ecosystem partnerships (e.g., official Astro/Vue integration) drive visibility. Framework-native image components will continue to dominate in single-framework projects.
Explore similar
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://unpic.pics
- Language
- TypeScript
- Last updated
- 16h ago
- Created
- 42mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Astro with Netlify adapter: respect value of `imageCDN` option
Using attribute aspectRatio inside react Image causes react warning
`srcset` does not preserve `operations.format` in `@unpic/core`, so forced formats like `webp` are ignored by responsive images
Astro 6 support
Top contributors
Similar repos
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
2.1k | +5 | TypeScript | 8/10 | 16h ago |
|
|
60.9k | — | TypeScript | 9/10 | -91 min ago |
|
|
1.2k | — | TypeScript | 8/10 | 3w ago |
|
|
13.9k | — | TypeScript | 8/10 | 1mo ago |
|
|
1.5k | — | TypeScript | 8/10 | 1d ago |
|
|
26.9k | — | TypeScript | 8/10 | 1w ago |
Next.js Image pre-renders or server-optimizes images, requires build-time integration, and generates wrapper elements. unpic-img offloads optimization to CDN and generates plain HTML; advantage for teams already using image CDNs, disadvantage for teams wanting integrated pipelines.
Nuxt Image is Nuxt-specific and includes server-side image optimization. unpic-img is framework-agnostic and CDN-centric; Nuxt Image wins for Nuxt-only projects, unpic-img for polyglot stacks.
ipx is an image proxy/optimizer middleware. unpic-img assumes CDN exists and generates URLs; ipx is for projects managing optimization server-side. Complementary rather than competing.
react-image is React-only, simpler, older. unpic-img spans multiple frameworks and includes modern features (srcset generation, CDN detection); broader but heavier.
Astro Image is integrated, framework-native. unpic-img offers multi-framework portability and explicit CDN reliance; Astro Image wins for Astro-only, unpic-img for mixed stacks.