Foxel.io
Buy

Use Shared Files Across Projects ​

Shared Files in Foxel are resources that can be reused across multiple projects.

Unlike project files, they are not tied to a single project. This makes them useful for building reusable libraries, presets, and workflow assets.

Why This Matters ​

Some resources should not have to be recreated every time you start a new project.

Shared Files solve that problem by making reusable content and presets available outside any single project.

Use them when something should become part of your general Foxel workflow instead of belonging only to one project.

What Shared Files Are ​

Shared Files are resources that can be used across multiple projects.

Unlike project files, they are not tied to a single project.

All Shared Files are stored in:

text
Documents\Foxel\Shared\

This makes them useful for reusable libraries, presets, scripts, and workflow resources.

How To Access Shared Files ​

Some Shared File types have dedicated workspace pages:

All other Shared File types can be accessed through:

File > Shared Files

It is recommended to manage Shared Files through Foxel’s user interface instead of the file explorer so changes are handled correctly.

Why Shared Files Are Useful ​

Shared Files help with reuse and consistency across projects.

They are useful for:

  • Reusing the same resources in multiple projects.
  • Keeping colors, materials, and presets consistent.
  • Building libraries of reusable content.
  • Storing scripts that should be available everywhere.
  • Reusing import, export, environment, and render-effect setups.
  • Improving workflow speed by avoiding repeated setup work.

Many shared resources also use Foxel’s own optimized file formats, which makes them better suited for repeated use inside Foxel.

Common Shared File Types ​

Foxel supports several Shared File categories, including:

Practical Examples ​

Shared Files are useful when you want to:

  • Reuse the same palette in many assets.
  • Keep material setups consistent across projects.
  • Use the same script in multiple projects.
  • Reuse export or import profiles.
  • Reuse environment or render-effect profiles.
  • Keep prefab or mini libraries available everywhere.
  • Build a personal library of workflow assets.

For example, if you use the same export settings for a game engine workflow in several projects, saving them as an Export Settings Profile avoids setting them up again each time.

Project Files vs Shared Files ​

A simple distinction is:

  • Project files belong to one project.
  • Shared Files are available across projects.

Use project files when the resource only matters inside one project.

Use Shared Files when the resource should be reused in multiple projects.

A Simple Rule ​

A useful rule of thumb is:

  • If something belongs only to one project, keep it in the project.
  • If something should be reusable across projects, make it a Shared File.

This keeps projects focused while still letting you build reusable libraries and presets over time.

What To Remember ​

  • Shared Files are reusable resources outside individual projects.
  • They live under Documents\Foxel\Shared\.
  • Most types are accessed through File > Shared Files.
  • Mini Sets and Prefab Packages use dedicated workspace pages.
  • Shared Files are useful for reuse, consistency, and reusable workflow setup.
  • Manage Shared Files through Foxel’s user interface when possible.

Copyright © 2017-present Minddesk GmbH