Pagination and load more Free & Pro

FileDeck splits long libraries into pages, and can present the split either as page numbers or as a load-more button — choose under Documents → Settings → Display. Both styles work in all three layouts and re-paginate automatically when visitors search or filter.

Setting how many documents show per page

Set the site-wide default with Documents per page under Documents → Settings → Display, and override it per library with the per_page attribute in the shortcode or the equivalent per-page control in the FileDeck Library block:

[filedeck per_page="20"]

With 87 documents and per_page="20", visitors get five pages. The right number depends on the layout: tables handle 20–50 rows comfortably, while grids usually look best with a per-page count that fills complete rows of cards, such as 12.

Page numbers or load more?

FileDeck offers two pagination styles, chosen with the Pagination setting under Documents → Settings → Display:

• Page numbers — numbered page links. Visitors can jump straight to any page, which suits reference libraries where someone may want "the older stuff."
• Load more button — a button that appends the next page below the current documents. This keeps everything on one continuously growing list and feels natural in grid layouts and on mobile.

Both styles use the same per-page value; they only differ in how the next page is presented. You can also let visitors pick their own page size: turn on the "documents per page" dropdown under Documents → Settings → Features and a dropdown appears above each library.

How paging interacts with search and filters

When a visitor types in the search box or picks a category or tag filter, the library re-paginates the matching results using the same per-page size. So a search that narrows 300 documents down to 34 matches shows those matches paged from page one, and clearing the search restores the original paging. Nothing is hidden by pagination — matches on "page 12" are found just the same. See instant search, sorting, and filters.

Large libraries page themselves sensibly

Paging, searching and filtering all run in the browser, so they happen with zero extra requests. Libraries with up to about 500 documents also ship an inlined instant-search index; beyond that the index is skipped, so search-as-you-type isn’t available in that library — scope large collections by category to keep it (see large libraries and performance). Your per_page setting works the same way regardless of library size.

FAQ

What is a good per_page value?

For tables, 20–50 rows. For grids, pick a multiple of your cards-per-row so pages end on complete rows — 12 is a common choice.

Does searching reset the page the visitor is on?

Results re-paginate from the first page of matches, which is what visitors expect — the most relevant view of the narrowed list starts at the top.

Do pagination and load more work in the folder layout?

Paging applies to FileDeck libraries in all layouts, though in the folder layout visitors mostly navigate by opening folders, so page size matters less there.