Skip to content

File Management Index

Here you will find everything related to file upload, file management and image processing. You will learn how to upload single or multiple files, delete or mov

A quick orientation to Assets Manager so you can understand reusable assets, media handling, and the bridge between files and UI resources.

Use this bridge when you want a quick orientation to Assets Manager before diving into broader file or frontend workflows. In Demo Dynamic Real Estate Site, Assets Manager is tied to real media folders that feed the listing cards you see in the sample app.

Use it to connect reusable assets with file organization, UI building, and publishing.

The live Assets tree is the practical starting point. In Demo Dynamic Real Estate Site, it exposes the actual assets hierarchy behind the sample app, including the listing images used by the property cards.

This step selects the real project_assets root node so the tour starts at the top of the live asset tree before drilling into the listing media folders used by the demo.

Move from the project root into the real /listings folder. In Demo Dynamic Real Estate Site, this folder contains the JPG files referenced by data.json, so selecting it ties Assets Manager directly to the media that powers the property-card images in the demo UI.

This step opens the real context menu on the selected assets root. That makes the overview practical immediately, because Create Folder, Rename, Delete, Upload, and Show in Explorer all operate from this live tree surface.

Close the context menu before continuing into broader file and frontend workflows so the overview leaves the manager in a clean state.

Start here for file-oriented work in Wappler: project files, assets, upload workflows, and the handoff into publish-safe habits.

Use this page as the file-oriented map through Wappler. Start with File Manager for the core project-file workflow, then branch into assets, upload/download workflows, or adjacent setup tasks depending on what kind of files you are managing.

The goal is to help beginners understand where project files live, where reusable assets are handled, and how file work connects to deployment.

Task-focused File Manager recipes: organize folders, upload assets safely, and handle external file changes.

Use these recipes when the job is to put files in the right place, keep the tree readable, and avoid surprises caused by hidden or externally changed files.

Create or organize folders before your project gets messy.
Upload assets into the folder structure you actually plan to maintain.
Refresh and inspect the tree before reacting to unexpected file changes.

Create folders before you need them desperately. A small amount of structure early prevents pages, assets, and support files from drifting into the project root.

Group related assets together.
Keep naming predictable.
Prefer tidy folders over later cleanup work.

Upload with intent. Put images, downloads, and support files where the rest of the team will expect them, not where they happen to land first.

Upload into the correct folder, not the nearest folder.
Check filenames before linking them from pages or actions.
Treat uploaded files as part of project structure, not temporary clutter.

When files changed outside Wappler, do not guess. Refresh the File Manager, confirm what moved or appeared, and only then decide whether the problem is a missing file, a build artifact, or a real accidental change.

Refresh before troubleshooting.
Confirm the exact folder and filename.
Use the hub or reference tour if you need UI orientation.

Return to the File Manager tours menu to continue with quick orientation, workflow guidance, or UI reference.

Use Quick Overview for spatial orientation.
Use General Usage for the day-to-day workflow.
Use Reference when you just need UI reminders.

Browse File Manager tours: quick overview, general usage, recipes, and reference.

Choose a File Manager tour to start. If you’re new, begin with Quick Overview.

Get a quick overview of File Manager: what it is, where to find it, and how it fits in your workflow.

File Manager is where you inspect the project folder structure that Wappler works with every day. It is the fastest place to answer a simple question: where is this file, and is it in the right place?

The tree gives you the real project shape: pages, includes, assets, server actions, and support files. When you understand this tree, navigation across Wappler becomes much easier.

Use the main toolbar for actions that change or refresh what you are looking at. This is where you create, upload, and refresh instead of hunting through menus first.

Treat File Manager as the source of truth for project organization. If files were changed outside Wappler, come back here, refresh, and confirm the tree before you continue editing.

The beginner takeaway is simple: use File Manager to stay oriented, open the right file, and keep your project structure clean before you move deeper into pages, workflows, or deployment.

Reference tour for the File Manager: file tree structure, toolbar controls, and best practices for organizing project files.

Use this reference tour as a navigation guide to File Manager before you start moving assets around. It shows which areas handle project files, uploads, and file actions, so you can tell where to work and what each part of the manager is responsible for when a project grows.

Use the tree to understand the real project structure.
Use the toolbar for create, upload, and refresh actions.
Refresh here first when something changed outside Wappler.

The tree is the primary navigation surface. Use it to confirm folder location, open the correct file, and spot unexpected structure changes quickly.

The toolbar groups the actions you use most often while managing files: create, upload, and refresh. Learn this strip once and most file-navigation work becomes faster.

The manager root is your orientation frame. When you are unsure whether a file issue is about structure, uploads, or external changes, start here and then drill into the tree or toolbar.

Continue with the File Manager overview for a guided start, or use General Usage and Recipes when you want more applied guidance.

Return to the File Manager hub.
Use General Usage for daily workflow habits.
Use Recipes for practical task patterns.

Typical File Manager workflow: browse folders, open files, and keep project assets organized.

A typical File Manager workflow is simple: find the right folder, open or create the file you need, then refresh if outside tools changed the project behind your back.

Start by navigating to the folder that matches the feature you are working on. Opening the right file from the right place prevents accidental edits in duplicate or generated files.

Use toolbar actions when you need a new file, a new folder, or an upload. The habit to build early is intention: put assets and support files in the place your future self will expect them.

If Git, a build tool, or another editor changed files outside Wappler, refresh here before assuming the tree is current. It is the quickest way to avoid acting on stale information.

Good file habits compound: clean structure makes Pages, Workflows, Git, and publishing easier because every other tool depends on the same project layout.