SLIDER DOCS

The ultimate FAQ and "good to know" list for Slider.

Watch Tutorial

About the Component

Do not remove the attributes. They are required for the Slider component to work.

Do not remove the attributes added to generated elements. If they are removed, the Solution will stop working.

Do not move the Slider elements outside the instance wrapper.

To keep the app functionality and edit mode working, keep all elements of the Slider component inside the instance element that wraps all Slider elements.

Do not export the code and host the website on an external server.

Currently, Webflow still doesn't allow us to export the website code with the script generated by our app needed to make the components work. In this case, if you export the code from Webflow and host your website on your own server, Finsweet Components will not function.

You can't preview the Slider functionality in Webflow Designer. Only on the published website.

The Slider will not function inside Webflow Designer because it requires JavaScript. Publish your project to webflow.io and see the Slider work properly.

You can't preview gaps and slides per view in Webflow Canvas. Only on the published website.

The 'space between the slides' and 'slides per view' are only visible on the published website. There will be not be any space between each slider in Designer.

‍

The Slider solution performs the required calculations to add the correct gaps and slides per view based on your Slider configuration. The gaps are calculated and added on the published page.

You can move Slider elements as long as you keep them inside the instance wrapper.

You can move the navigation arrows and pagination wrapper to other positions. It is required to keep all moved elements inside the instance wrapper.

You can make changes to classes generated by Finsweet Slider.

Finsweet Components doesn't rely on classes to work. You can change, rename, and duplicate classes however you want. You have full control over the class organization and naming convention of your Slider..

You can edit any Slider by selecting the instance wrapper and opening the app.

You can enter "edit mode" for any Component by selecting the component in Webflow Designer and opening Finsweet Components. You can change many options to update your Slider at any point in the development process.

‍

To prevent Component issues, some options are disabled in edit mode. If you need a disabled option, please generate a new Slider.

You can manually copy/paste the Slider Component in Webflow Designer as many times as you want.

You can select any Slider instance wrapper, copy it to clipboard, and paste it inside the same Webflow project.

About styling & interactions

Style and customize the Slider component however you want.

Use the Webflow Style panel to customize your slider elements, such as slides, pagination, and navigation. There are no design limitations for Finsweet Components.

To style the Active Slide, add a combo class  is-slide-active  to the slide item.

Our solution adds the combo class is-active-slide by default to the active slide on the published website. You can style the is-active-slide class however you want to show the active slide state.

‍

You can optionally change the name of the active slide class in the configure tab.

Change the transition of active states using the native 'transitions' property in the Webflow Style panel.

Add transitions to create smoother changes between slide states. You can get creative here!

You can not add interactions to specific elements inside the slides.

Currently, our solution does not support Webflow interactions to animate specific elements inside the slides in the active state. However, you can achieve this using custom CSS or a creative implementation of the Thumbs and Controller feature.

How Slider technically works

The Slider is built on top of the Swiper.js library

Our slider is built on top of the most powerful and flexible open-source slider library, Swiper.js.

‍

Instead of reinventing the wheel, we chose to build on top of Swiper for its extensive feature set and reliability in creating responsive, touch-enabled sliders. The most capable slider tool is now completely customized for our normal workflow inside Webflow.

Swiper.js uses pixel instead of REMs

Swiper.js relies on pixel measurements for its calculations, rather than using REM units. This design choice ensures precise and consistent behavior across various devices and screen sizes. However, it means that our slider's responsiveness and layout are directly tied to pixel-based measurements, which may affect flexibility when working with REM-based designs. As this is an inherent characteristic of swiper.js, we have no control over this aspect.

About the plans

Is there a limit to the number of instances of a Component per project?

No, there is no limit to the number of instances of a Component you can use in a Webflow project. As long as you have a subscription or a Single Site Lifetime plan, you can use as many instances of the Component as you want in your published website.

Is there a limit to the number of Component loads on a website?

No, there is no limit to the number of loads on a website. Both staging and custom domains support unlimited loads per month.

Do I need a paid plan to use the Finsweet Components app?

No, the Finsweet Components app is free to access and use. You do not need a paid plan to generate the Components in Webflow canvas and publish them to your staging webflow.io domain. However, you will need a paid plan if you want to publish Components on your custom domain.

How can I instruct my client to get a subscription for their project?

In your client's project, open the Finsweet Components app and click the 'Get a subscription' button to go to the checkout page. Copy the checkout link and send it to your client so they can complete the purchase. After the payment is complete, your client will still need to open the subscription and connect the domain that will use the Components.

Can I use Components in a Webflow project connected to multiple custom domains?

Yes, Components will work normally in a Webflow project connected to multiple custom domains, as long as you have an active plan connected to one of the domains in use.

Do Components work on websites with a reverse proxy?

Yes, Finsweet Components work normally on websites using a reverse proxy, as long as you have a paid plan connected to the domain.

What is a Single Site Lifetime plan?

Finsweet Components with a Single Site Lifetime plan will work on the published website forever after a one-time payment. You purchase a Single Site Lifetime plan, set the domain name, and the Component will work on that domain permanently — with no additional costs or future payments.

You can have a Single Site Lifetime plan for a specific Component or for a bundle that includes all Components.

What happens if my domain name changes when using a Single Site Lifetime plan?

You can change your domain name at any time in the future, as long as it's for the same project or company. When you're buying Single Site Lifetime plan, you're buying the ability to use the Component for the lifetime of the project. We'll be lenient with domain changes, but will not allow abuse of the pricing model. We will not accept domain name changes that are clearly for different projects.

Will new Components released in the future be included in the All Components Bundle plan?

Yes, new Components added to the Finsweet Components app will work automatically when released, in case you have an All Components Bundle plan connected to your website.

The price of the All Components Bundle plan will increase as new Components are added to the app, so this is a great way to lock in a lower price for your website.

Can I change domain names using an Agency Plan?

Yes, you are free to change domain names at any time if you have an Agency Plan.

How do Agency Plans work?

Agency Plans are yearly subscriptions that allow you to use unlimited Components in a specific number of projects per year, along with extra Library features. These include sharing access to the Library with your team, creating folders, and saving Components to the Library.

For example, with the Agency Lite Plan, you can use all our Components in 24 websites in the first year. When your plan renews the following year, you will receive 24 more licenses. Any unused license will roll over into the new subscription cycle.

Can I cancel my Agency Plan subscription at any time?

Yes, you can schedule the cancellation of your Agency Plan yearly subscription at any time. Your subscription will remain active and function normally until the end of your billing period. After that, it will be cancelled. All domains connected to the cancelled subscription will continue working normally, forever.

What happens if I purchase an Agency Plan and change my mind?

We offer a 100% refund policy within the first month of your Agency Plan purchase. If you change your mind within the first 30 days, you can request a full refund. We do not offer refunds after the 30-day trial period.

Note: If a refund is issued, the domains connected to the refunded plan will stop working.

Why are monthly subscriptions not allowed for Agency Plans?

Good question. We decided to allow only yearly payments to build long-term relationships with our users, reduce the need for additional controls, and prevent abuse.

Why is the Cookie Consent Component not included in the Agency Plans?

The Cookie Consent Component is not included in Agency Plans because it will be migrated to a new product soon. This new product will have its own pricing model. See the full announcement here.

Can I downgrade my Agency Plan?

Yes, you can downgrade your Agency Plan at any time. The changes to how your plan works and the number of available domains will take effect at the end of your billing period. When you downgrade to a more limited plan, the only change is that you will have fewer domains available to use in the following year. All domains from your current Agency Plan will remain available.

For example, if you have an Agency Pro plan with 48 websites/domains per year and downgrade to the Lite plan with 24 websites/domains per year, you will still keep your 48 domains from the current plan. In the following year, your new Lite plan will give you 24 new domains to use.

What happens if I use all the domains available in my Agency Plan?

If you reach the domain limit of your Agency Plan, you have two options: upgrade to a higher Agency Plan with more domains available per year, or purchase individual Single Site Lifetime plans.

What if my domain name changes in my current monthly or annual subscription?

If you have an active monthly or annual subscription, you can change your domain name at any time while your subscription is active. To use your subscription with a different domain, go to my.finsweet.com/subscriptions, find your subscription, and update your site domain URL.

What will happen to my current subscription for all components?

The special launch offer with the 'all components' subscription is no longer available. Subscribers to this plan will keep the $10 monthly price for all current and future components as long as they maintain the subscription.

What happens if my current monthly or annual subscription expires?

If your monthly or annual subscription expires, the Components used on your website will stop working. They will resume working when you reactivate your subscription. We will reach out to you many times before 'turning off' Finsweet Components in your project. We will not show a broken Component on your project. Instead, we will completely remove the entire Component from the page.

Do I have access to Consent Pro with my legacy All Components subscription?

Yes, if you have the legacy All Components subscription, you will continue to have access to all Finsweet components, including Cookie Consent and Consent Pro.

Will my current Cookie Consent plans migrate to the new Consent Pro app?

Yes. All current Cookie Consent licenses will be migrated automatically to Consent Pro. If you are an active user of Finsweet Components - Cookie Consent, the Consent Pro app will work normally for you, with no migration process needed.

Still need help?

Get Support
Watch Tutorial