Skip to main content
Fileloom maintains a complete version history of your templates, allowing you to track changes and restore previous versions.

​
How Versioning Works

​
Drafts

  • Changes are auto-saved as a draft
  • Drafts are not available via API
  • Only one draft exists at a time (your current work)
  • Draft shows as “Current Draft” in version history

​
Published Versions

  • Created when you click Publish
  • Each publish creates a new version number
  • Published versions are available via API
  • All versions are preserved indefinitely

​
Version History Panel

Access version history from the template editor:
  1. Click the Version History button (clock icon)
  2. View all versions with timestamps
  3. Click any version to preview it

​
Version List

ColumnDescription
VersionVersion number (v1, v2, v3…)
PublishedWhen the version was published
Published ByTeam member who published
StatusCurrent (active) or Previous

​
Viewing Previous Versions

Click on any version to see:
  • HTML content at that version
  • CSS content at that version
  • Test data at that version
  • Preview of the rendered PDF
Viewing a previous version doesn’t affect your current draft or the active published version.

​
Restoring a Version

To restore a previous version:
1

Open Version History

Click the Version History button in the editor.
2

Select Version

Click on the version you want to restore.
3

Click Restore

Click “Restore This Version” to load it into the editor.
4

Review Changes

The restored content becomes your current draft. Review and make any adjustments.
5

Publish

Click Publish to make the restored version active. This creates a new version number.
Restoring a version replaces your current draft. If you have unsaved work, save or publish it first.

​
API and Versions

​
Default Behavior

API requests use the latest published version of a template: 
{
  "templateId": "tpl_abc123",
  "templateData": { ... }
}

​
Current Draft

Drafts are never used by the API. Always publish your template to make changes available.

​
Best Practices

​
Meaningful Publishes

Don’t publish after every small change. Instead:
  • Make a series of related changes
  • Test thoroughly with different data
  • Publish when the template is ready for use

​
Document Changes

While Fileloom doesn’t have built-in change notes, consider:
  • Adding a comment in your HTML: <!-- v3: Added tax calculation -->
  • Maintaining a changelog in your project documentation

​
Test Before Publishing

Always test your template with various data scenarios:
  • Empty arrays
  • Long text that might wrap
  • Missing optional fields
  • Edge cases (zero amounts, special characters)

​
Version Limits

There are no limits on the number of versions. All published versions are retained for the lifetime of the template.

​
Deleting Templates

When you delete a template:
  • All versions are permanently deleted
  • The template ID becomes invalid
  • API requests using that template will fail
Template deletion cannot be undone. Consider exporting important templates before deletion.

​
Exporting Templates

To back up a template:
  1. Open the template in the editor
  2. Copy the HTML content
  3. Copy the CSS content
  4. Save both locally or in version control
For programmatic backup, you can fetch template content via the dashboard and store in your own version control system.