Svelte wins 4 of 6 categories, Solid 2, none tiedEdge cases join the count once you run the live tests below. They are measured in your browser, not stored here.
Edge cases
Not run yetFour everyday situations running side by side in your browser. Press Run on a case and read what happens; nothing here is recorded in advance.Stale response overwrites fresh oneClick through a list faster than the server answers.RunSolid○Not run yetSvelte○Not run yetShow the code10,000 rows of irregular heightScroll a long list where every row has a different height.RunSolid○Not run yetSvelte○Not run yetShow the codeSubscriptions after 100 mount cyclesMount and unmount a subscribed component a hundred times.RunSolid○Not run yetSvelte○Not run yetShow the codeOne broken item takes down the treePut malformed data into one card out of twenty.RunSolid○Not run yetSvelte○Not run yetShow the code
Code
Solid 3 of 4, Svelte 1 of 4 · Solid aheadHow much there is to read, and how much of it belongs to somebody else.SolidSvelteLines of code (TodoMVC)——Not counted: no data for SolidFewer lines to read when someone else picks the project up. Counts the code you write and maintain yourself, not a stylesheet you installed from npm.npm packages shipped12Solid is 50% below SvelteHow many npm packages end up inside the bundle the browser downloads. This is code your users execute, not code your build machine reads.Distinct `node_modules/<package>` paths in the `sources` of the production build sourcemaps. Scaffolded on 2026-08-13 with each framework's own getting-started command: react `npm create vite@latest app -- --template react-ts`; vue `npm create vue@latest app -- --default`; svelte `npx sv create app --template minimal --types ts --no-add-ons --install npm`; solid `npm create solid@latest app -- --vanilla --ts --template basic`; angular `npx @angular/cli@21 new app --defaults --skip-git --package-manager=npm`; $mol `git clone --depth 1 https://github.com/hyoo-ru/mam.git app && npm install`. For $mol, the sourcemap of the deployed todomvc.hyoo.ru bundle.Soliddocs.solidjs.com/quick-start2026-08-13Sveltesvelte.dev/…/creating-a-project2026-08-13Dev dependencies declared57Solid is 29% below SveltePackages the starter project names in its own package.json. Build-time tooling included: this is the list your development environment inherits, not what reaches the browser.Entries in `dependencies` plus `devDependencies` of a fresh starter project. Scaffolded on 2026-08-13 with each framework's own getting-started command: react `npm create vite@latest app -- --template react-ts`; vue `npm create vue@latest app -- --default`; svelte `npx sv create app --template minimal --types ts --no-add-ons --install npm`; solid `npm create solid@latest app -- --vanilla --ts --template basic`; angular `npx @angular/cli@21 new app --defaults --skip-git --package-manager=npm`; $mol `git clone --depth 1 https://github.com/hyoo-ru/mam.git app && npm install`.Soliddocs.solidjs.com/quick-start2026-08-13Sveltesvelte.dev/…/creating-a-project2026-08-13Dev packages installed7022Svelte is 69% below SolidHow many separate packages npm resolves into node_modules on a clean checkout. Each one is an author your build trusts, and every CI run downloads all of them.Distinct name+version pairs in `npm ls --all` after scaffolding and installing the starter project. Scaffolded on 2026-08-13 with each framework's own getting-started command: react `npm create vite@latest app -- --template react-ts`; vue `npm create vue@latest app -- --default`; svelte `npx sv create app --template minimal --types ts --no-add-ons --install npm`; solid `npm create solid@latest app -- --vanilla --ts --template basic`; angular `npx @angular/cli@21 new app --defaults --skip-git --package-manager=npm`; $mol `git clone --depth 1 https://github.com/hyoo-ru/mam.git app && npm install`.Soliddocs.solidjs.com/quick-start2026-08-13Sveltesvelte.dev/…/creating-a-project2026-08-13node_modules size65 MB68 MBSolid is 4.4% below SvelteDisk footprint of a fresh checkout. None of it ships to the browser, but all of it is downloaded by every CI run and every new machine on the team.`du -sk node_modules` after scaffolding and installing the starter project. Scaffolded on 2026-08-13 with each framework's own getting-started command: react `npm create vite@latest app -- --template react-ts`; vue `npm create vue@latest app -- --default`; svelte `npx sv create app --template minimal --types ts --no-add-ons --install npm`; solid `npm create solid@latest app -- --vanilla --ts --template basic`; angular `npx @angular/cli@21 new app --defaults --skip-git --package-manager=npm`; $mol `git clone --depth 1 https://github.com/hyoo-ru/mam.git app && npm install`.Soliddocs.solidjs.com/quick-start2026-08-13Sveltesvelte.dev/…/creating-a-project2026-08-13
Weight and loading
Solid 0 of 1, Svelte 1 of 1 · Svelte aheadWhat the browser downloads, and how long it waits before the page reacts.SolidSvelteTodoMVC bundle, gzip——Not counted: no data for SolidWhat the browser actually downloads for a small but complete application, compressed the way a server would send it.Startup transfer150 KB146 KBSvelte is 2.4% below SolidBytes pulled over the network before the benchmark application is usable. Same application in every column, so the difference is the framework.Lighthouse total byte weight for the js-framework-benchmark application, reported as benchmark 34_startup-totalbytes. Transfer size, not gzip specifically.Solidnin-jin.github.io/…/table.html2022-02-05Sveltenin-jin.github.io/…/table.html2022-02-05
Speed
Solid 2 of 7, Svelte 4 of 7 · Svelte aheadHow long changes take to reach the screen, and how much memory is held while they do.SolidSvelteCreate 1,000 rows153 ms173 msSolid is 12% below SvelteTime to put a thousand fresh rows on the screen. This is the wait after hitting a filter or opening a list.js-framework-benchmark 01_run1k, arithmetic mean of 10 runs.Solidnin-jin.github.io/…/table.html2022-02-05Sveltenin-jin.github.io/…/table.html2022-02-05Partial update992 ms977 msSvelte is 1.5% below SolidTouching every tenth row of a thousand, sixteen times. This is where a framework either finds the changed rows or re-checks everything.js-framework-benchmark 03_update10th1k_x16, arithmetic mean of 10 runs.Solidnin-jin.github.io/…/table.html2022-02-05Sveltenin-jin.github.io/…/table.html2022-02-05Swap two rows181 ms173 msSvelte is 4.6% below SolidTwo rows trade places out of a thousand. The ideal answer is two DOM moves, and the gap here shows who gets close to it.js-framework-benchmark 05_swap1k, arithmetic mean of 10 runs.Solidnin-jin.github.io/…/table.html2022-02-05Sveltenin-jin.github.io/…/table.html2022-02-05Remove one row45.3 ms36.2 msSvelte is 20% below SolidDeleting a single row out of a thousand. The smallest possible change, so it measures the fixed cost of reacting at all.js-framework-benchmark 06_remove-one-1k, arithmetic mean of 10 runs.Solidnin-jin.github.io/…/table.html2022-02-05Sveltenin-jin.github.io/…/table.html2022-02-05Memory after load1.22 MB1.22 MBBoth report the same valueHeap the framework occupies with nothing on the page yet.js-framework-benchmark 21_ready-memory, single run.Solidnin-jin.github.io/…/table.html2022-02-05Sveltenin-jin.github.io/…/table.html2022-02-05Memory with 1,000 rows1.94 MB2.14 MBSolid is 9.3% below SvelteHeap once a thousand rows are on screen. On a phone this is the difference between staying alive in the background and being killed.js-framework-benchmark 22_run-memory, single run.Solidnin-jin.github.io/…/table.html2022-02-05Sveltenin-jin.github.io/…/table.html2022-02-05Startup blocking time20.7 ms10.1 msSvelte is 51% below SolidHow long the main thread is busy during startup, so taps and scrolls do nothing.js-framework-benchmark 32_startup-bt (Lighthouse total blocking time), arithmetic mean of 4 runs.Solidnin-jin.github.io/…/table.html2022-02-05Sveltenin-jin.github.io/…/table.html2022-02-05
Built in
Solid 0 of 10, Svelte 1 of 10 · Svelte aheadWhether the framework ships it, or you reach for a library.SolidSvelteRouterYesYesBoth have itWhether URLs and navigation come from the framework project itself, or you go pick a library and own that choice forever.Built in means the framework project ships it itself: its own package, or one the same team maintains and publishes as official. A library from anyone else counts as no, however popular or de-facto standard it has become, which is why routing is a yes for Angular and a no for React. The same cut is applied to all six frameworks, and every value links to the official page it was read from. Yes when that project publishes and documents a routing solution of its own. No when its own docs send you to a third-party project instead.Soliddocs.solidjs.com/solid-router2026-08-13Sveltesvelte.dev/…/routing2026-08-13LocalizationNoNoNeither has itTranslating an application is rarely planned at the start and always arrives later.Built in means the framework project ships it itself: its own package, or one the same team maintains and publishes as official. A library from anyone else counts as no, however popular or de-facto standard it has become, which is why routing is a yes for Angular and a no for React. The same cut is applied to all six frameworks, and every value links to the official page it was read from. Yes when that project publishes and documents localization of its own. An official CLI add-on that wires up somebody else’s i18n library is a no, because the library is still somebody else’s.Soliddocs.solidjs.com2026-08-14Sveltesvelte.dev/…/paraglide2026-08-14ThemingNoNoNeither has itDark mode and brand colours without inventing your own CSS variable convention.Built in means the framework project ships it itself: its own package, or one the same team maintains and publishes as official. A library from anyone else counts as no, however popular or de-facto standard it has become, which is why routing is a yes for Angular and a no for React. The same cut is applied to all six frameworks, and every value links to the official page it was read from. Yes when that project publishes and documents a theming mechanism of its own. No when the word does not appear in its official API reference, which is the page linked, so the absence can be checked directly.Soliddocs.solidjs.com2026-08-13Sveltesvelte.dev/…/overview2026-08-13List virtualizationNoNoNeither has itLong lists stay smooth because off-screen rows are never rendered. Without it, someone eventually bolts a library onto a list that already shipped.Built in means the framework project ships it itself: its own package, or one the same team maintains and publishes as official. A library from anyone else counts as no, however popular or de-facto standard it has become, which is why routing is a yes for Angular and a no for React. The same cut is applied to all six frameworks, and every value links to the official page it was read from. Yes when that project publishes and documents lazy or virtual rendering of long lists. No when no such component appears in its API reference.Soliddocs.solidjs.com2026-08-14Sveltesvelte.dev/…/overview2026-08-14Offline supportNoYesSvelte yes, Solid noA service worker set up by the framework rather than copied from a blog post.Built in means the framework project ships it itself: its own package, or one the same team maintains and publishes as official. A library from anyone else counts as no, however popular or de-facto standard it has become, which is why routing is a yes for Angular and a no for React. The same cut is applied to all six frameworks, and every value links to the official page it was read from. Yes when that project ships the service worker integration: a module it builds and registers for you. No when the docs only show where to drop your own sw.js and how to register it with the browser API, because that is the browser’s feature rather than the framework’s.Soliddocs.solidjs.com/…/service-workers2026-08-14Sveltesvelte.dev/…/service-workers2026-08-13Server renderingYesYesBoth have itRendering to HTML on the server, for search engines and for the first paint.Built in means the framework project ships it itself: its own package, or one the same team maintains and publishes as official. A library from anyone else counts as no, however popular or de-facto standard it has become, which is why routing is a yes for Angular and a no for React. The same cut is applied to all six frameworks, and every value links to the official page it was read from. Yes when that project publishes and documents a server rendering API of its own. No when its published module list contains no such module.Soliddocs.solidjs.com/…/render-to-string2026-08-13Sveltesvelte.dev/…/page-options2026-08-13Tests without a DOMNoNoNeither has itComponents testable as plain objects, with no browser and no jsdom to boot up first.Built in means the framework project ships it itself: its own package, or one the same team maintains and publishes as official. The same cut is applied to all six frameworks, and every value links to the official page it was read from. Yes when a component can be instantiated and asserted on with no document in play — the test never reaches for one. No when a DOM has to exist before a component can render at all, which is what every official testing guide here prescribes when it tells you to install jsdom, happy-dom or a browser. The question is whether a DOM is required, not whether the runtime happens to have one available: a runtime that provides a document nobody asks for does not make the test a DOM test.Soliddocs.solidjs.com/guides/testing2026-08-13Sveltesvelte.dev/…/testing2026-08-13Dependency injectionYesYesBoth have itSwapping a real service for a fake one in a test without touching the component that uses it.Built in means the framework project ships it itself: its own package, or one the same team maintains and publishes as official. A library from anyone else counts as no, however popular or de-facto standard it has become, which is why routing is a yes for Angular and a no for React. The same cut is applied to all six frameworks, and every value links to the official page it was read from. Yes when that project documents a way to hand a component a value from outside it and replace that value later, in a test or in another host. Context APIs count: the bar is a documented mechanism, not a particular shape of container.Soliddocs.solidjs.com/…/create-context2026-08-14Sveltesvelte.dev/…/context2026-08-14FormsYesYesBoth have itValidation, dirty state and submission handled by the framework instead of a fourth form library per team.Built in means the framework project ships it itself: its own package, or one the same team maintains and publishes as official. A library from anyone else counts as no, however popular or de-facto standard it has become, which is why routing is a yes for Angular and a no for React. The same cut is applied to all six frameworks, and every value links to the official page it was read from. Yes when that project documents a form API that goes past binding one input to one variable, covering at least submission handling or validation state. Two-way binding on its own is a no.Soliddocs.solidjs.com/…/action2026-08-14Sveltesvelte.dev/…/form-actions2026-08-14Typed templatesYesYesBoth have itA typo in a template is caught by the compiler, not by a user.Built in means the framework project ships it itself: its own package, or one the same team maintains and publishes as official. A library from anyone else counts as no, however popular or de-facto standard it has become, which is why routing is a yes for Angular and a no for React. The same cut is applied to all six frameworks, and every value links to the official page it was read from. Yes when the framework’s official TypeScript documentation covers type checking of its template or view layer.Soliddocs.solidjs.com/configuration/typescript2026-08-13Sveltesvelte.dev/…/typescript2026-08-13
Ecosystem and market
Solid 0 of 4, Svelte 4 of 4 · Svelte aheadHow easy it is to hire for it, to search for it, and to find a ready-made part.SolidSvelteGitHub stars35,81687,975Svelte is 2.5× SolidA popularity signal, and nothing more. It says how many people bookmarked the repository, not how many shipped with it.`stargazers_count` from the GitHub API for the repository that holds the framework's current source.Solidgithub.com/solidjs/solid2026-08-13Sveltegithub.com/sveltejs/svelte2026-08-13npm downloads3,456,458 per week5,273,631 per weekSvelte is 53% above SolidThe closest thing to a usage count. Inflated by CI runs, but inflated the same way for everyone.npm registry downloads for the last full week, for the package you install to use the framework.Solidapi.npmjs.org/…/solid-js2026-08-13Svelteapi.npmjs.org/…/svelte2026-08-13Stack Overflow questions3236,281Svelte is 19.4× SolidHow likely it is that your problem was already asked and answered by someone else.Question count of the framework's Stack Overflow tag, via the Stack Exchange API.Solidstackoverflow.com/…/solid-js2026-08-13Sveltestackoverflow.com/…/svelte2026-08-13npm maintainers13Svelte is 3× SolidHow many people can publish a release. A low number is a bus factor.Length of the `maintainers` array in the npm registry metadata of the framework's primary package.Solidregistry.npmjs.org/solid-js2026-08-13Svelteregistry.npmjs.org/svelte2026-08-13
Cost of ownership
Solid 2 of 3, Svelte 0 of 3 · Solid aheadWhat the dependency tree and the release history ask for over the years.SolidSvelteAdvisories in shipped packages00Both report the same valueKnown vulnerabilities in the packages that reach the browser. These execute on your users’ machines, which makes them a different class of risk from anything in the build toolchain.Each shipped package, at its installed version, queried against the OSV database. Counts packages carrying at least one advisory.Soliddocs.solidjs.com/quick-start2026-08-13Sveltesvelte.dev/…/creating-a-project2026-08-13Advisories in the dev tree03Solid has none, Svelte has 3Known vulnerabilities in the packages a fresh checkout installs. These run on developer and CI machines rather than in the browser, but somebody still has to triage every one.Total reported by `npm audit` on the starter project, straight after scaffolding it. Scaffolded on 2026-08-13 with each framework's own getting-started command: react `npm create vite@latest app -- --template react-ts`; vue `npm create vue@latest app -- --default`; svelte `npx sv create app --template minimal --types ts --no-add-ons --install npm`; solid `npm create solid@latest app -- --vanilla --ts --template basic`; angular `npx @angular/cli@21 new app --defaults --skip-git --package-manager=npm`; $mol `git clone --depth 1 https://github.com/hyoo-ru/mam.git app && npm install`.Soliddocs.solidjs.com/quick-start2026-08-13Sveltesvelte.dev/…/creating-a-project2026-08-13Breaking releases in 3 years01Solid has none, Svelte has 1Major versions shipped since 2023. Every one of them is a migration someone on the team pays for.Count of major semver versions of the framework's primary npm package first published in the last three years. Left blank for packages that do not use semver majors.Solidregistry.npmjs.org/solid-js2026-08-13Svelteregistry.npmjs.org/svelte2026-08-13
How this is measured
Every value here comes from a measurement or from an outside source, and carries the link and the date it was taken with it. A metric counts towards a category only when both frameworks report it: otherwise the one with the fuller table would win on how complete its data is rather than on what the numbers say. Where nobody has measured yet, the row says so instead of guessing.Methodology and sources on GitHub
Suggest a framework
Missing one? Name it and open an issue. Adding a framework means a data file with its measurements, and, for the live tests, a runner page — both live in the repository next to the ones already here.Open an issueType to search the documentation.
