Open-source project
alvarotrigo/fullPage.js avatar
alvarotrigo/fullPage.js

fullPage.js 4.0.41: Full-Screen Scroll Sites, GPLv3, and the Cost of That Convenience

fullPage plugin by Alvaro Trigo. Create full screen pages fast and simple

35,355 stars7,055 forksJavaScriptGPL-3.0

At a glance

What is it?
fullPage.js turns a page into fixed viewport sections with horizontal sliders, but its GPLv3 license and extension model shape where it fits. This review covers the mechanism, setup, limits, and the commercial alternative.
Who is it for?
Adopt fullPage.js if you need a full-screen sectioned layout with touch support and have a GPLv3-compatible open source project, or if you buy a commercial license for proprietary work. Avoid it if your project must stay MIT or Apache licensed, or if you only need a single full-screen hero and not an entire scroll-jacking experience.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 56 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • alvarotrigo/fullPage.js35,355 ★ · -53
Star history
Repository2026-08-182026-11-15
alvarotrigo/fullPage.js35.4k35.4k

-53 Stars in the last 89 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What fullPage.js Actually Does

fullPage.js is a JavaScript library that turns a webpage into a sequence of full-screen sections. Each section fills the viewport, and scrolling moves you from one section to the next. It also supports landscape sliders inside those sections, so a single section can contain multiple horizontal panels. The README describes it as creating "fullscreen scrolling websites" and adding "landscape sliders inside the sections of the site." The target user is a front-end developer building a one-page marketing site, a portfolio, or a presentation-style page who does not want to hand-roll scroll snapping and touch gesture handling. The library handles the core mechanics, so you can focus on the content inside each section.

How the Scroll Mechanism Works

The core idea is that the page is divided into sections, usually via HTML elements with a class like `section`. fullPage.js measures the viewport height and sets each section to that height. When the user scrolls, the library intercepts the scroll event and animates the transition to the next section. The README mentions an option called `css3`, which suggests two animation paths: one using CSS3 transforms for smooth, GPU-accelerated transitions, and another using JavaScript-based animation. If `css3:false`, you can add an optional easing file to use easing effects other than the default `easeInOutCubic`. The library also adds state classes to sections and slides, so you can style the active section differently. Touch support is built in for mobile phones, tablets, and touch screens.

Getting It Running: Commands and Files

Installation is either via npm or bower. The README shows `npm install fullpage.js` or `bower install fullpage.js`. You then include two files: `fullpage.js` (or `fullpage.min.js`) and `fullpage.css`. A minimal HTML setup would link the stylesheet and the script, then initialize the plugin on a container element. The required HTML structure is sections inside a wrapper, and the README references example files for the exact markup. You can also load it from a CDN like JSDelivr or UNPKG. For module loaders, the wiki covers Webpack, Browserify, and Require.js usage. The setup is simple: include two files, add the right HTML structure, and call the constructor with options.

Key Options and Callbacks

The README lists sections for Options, Methods, and Callbacks. It mentions `css3` as a boolean option that controls whether CSS3 transforms are used. What is confirmed is that the library provides state classes, which you can use for styling. The README also mentions lazy loading, auto play/pause for embedded media, and the ability to create smaller or bigger sections. The point is that the library is configurable, but the README alone does not give you the full option surface.

The GPLv3 License Is the Real Constraint

The license is the most important factor for adoption. fullPage.js is released under GPLv3 for open source use. That means if you use it in an open source project, your entire project must be GPLv3-compatible. The README states: "If you are creating an open source application under a license compatible with the GNU GPL license v3, you may use fullPage under the terms of the GPLv3." It also requires you to keep the credit comments in the JavaScript and CSS files intact, even after minification. If you do not want to open-source your code, you must buy a commercial license. The README explicitly says the commercial license is for "non open sourced sites, themes, projects, and applications." This is not a permissive MIT-style license. For a company building a proprietary product, the commercial license is a hard cost. For a developer who just wants a quick demo, GPLv3 might be fine, but it is a legal commitment that you should not ignore.

Limitations and Wrong Use Cases

fullPage.js is not a general-purpose layout tool. It forces a specific interaction model: full-screen sections with scroll snapping. If your content is longer than a viewport, you need to handle overflow carefully. The library also hijacks the default scroll behavior, which can be disorienting for users who expect normal scrolling. It is a poor fit for content-heavy pages like documentation or blog posts. The README also notes that IE 11 is supported, but for IE < 11 you must use fullPage.js v3. The v4 version has dropped support for older IE. So if you have legacy browser requirements, you are stuck on an older version.

Alternatives: scroll-snap and Swiper

The most direct alternative is native CSS scroll snap. Modern browsers support `scroll-snap-type` and `scroll-snap-align`, which let you achieve full-screen section snapping without any JavaScript. The difference is that CSS scroll snap does not hijack the scroll event in the same way; it lets the browser handle the physics, and it does not provide callbacks, state classes, or a slider mechanism out of the box. You would need to build those yourself. Another alternative is Swiper, a library that is MIT-licensed and focuses on sliders, including full-screen vertical slides. Swiper does not have the GPLv3 constraint, so it is easier to adopt in proprietary projects. The trade-off is that Swiper is primarily a slider library, not a full-page scroll framework, so you would need to configure it differently for section-based navigation. The choice comes down to whether you need the scroll-jacking behavior and the GPLv3 is acceptable, or whether you prefer a permissive license and are willing to handle more of the scroll logic yourself.

Maintenance and Upgrade Costs

The repository is actively maintained, with the latest release on 2026-03-04 and previous releases in December 2025. The README includes a migration guide from v3 to v4, which indicates that upgrades are not always drop-in. The v4 release likely changed the API or behavior, so moving from v3 to v4 requires effort. The README also links to an extensions page, so check there whether what you need is part of the core library. The maintenance cost is not just keeping the library updated, but also ensuring your code works with each new release. Since the project is actively pushed, you should track the changelog and test upgrades in a staging environment. The GPLv3 requirement to keep credit comments intact also means you must be careful when minifying or bundling, as those comments could be stripped by aggressive build tools.

Editorial conclusion

Adopt fullPage.js if you need a full-screen sectioned layout with touch support and have a GPLv3-compatible open source project, or if you buy a commercial license for proprietary work. Avoid it if your project must stay MIT or Apache licensed, or if you only need a single full-screen hero and not an entire scroll-jacking experience. Before committing, verify the exact GPLv3 obligations for your distribution method and check which extensions you need, since the core library alone may not cover your use case.

Frequently asked questions

What is fullPage.js?

The README describes it as a simple library that creates fullscreen scrolling, onepage websites and adds landscape sliders inside the sections of the site, available as a core JavaScript library plus separate React, Vue and Angular wrappers.

Is fullPage.js free?

It is free under the GPLv3 open source option, provided the project is open source under a GPL-compatible license and keeps fullPage.js's credit comments intact in the JavaScript and CSS files; proprietary or closed-source use requires the separate Commercial license instead.

Is there a free alternative to fullPage.js?

fullPage.js itself is free under its GPLv3 option for open source projects. The same fullscreen scrolling effect, without the nested landscape sliders or the library's callbacks, can be built with native CSS scroll-snap and no library at all.

How do you open a full screen window in JavaScript with fullPage.js?

The README's Usage section says to include the fullpage.js script and fullpage.css stylesheet on the page, then initialize the library against the page's sections as documented there, rather than using the browser's own Fullscreen API directly.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/alvarotrigo-fullpage-js.svg)](https://hysenlabs.com/projects/alvarotrigo-fullpage-js)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/alvarotrigo-fullpage-js.svg)](https://hysenlabs.com/projects/alvarotrigo-fullpage-js)

Was this useful?