FreENEXt Beta Guide
Invited conversion beta

Test with a copy, verify everything

FreENEXt is beta software. Use an exported copy of your notes, never your only or original data. Keep the source export unchanged until you have inspected the downloaded vault and its conversion report.

Who should test

This is an invited conversion beta. Testing access is by invitation only. Do not share this guide as a general public sign-up.

Invited tester profile

People comfortable exporting data, opening a ZIP, comparing Markdown and attachments, and reporting a reproducible result without sharing private note content.

Start small

Use 5-20 representative notes first: plain text, links, tags, nested pages, and a few attachments. Large or irreplaceable archives should wait until the sample output is correct.

Browser coverage

Current Chrome and Edge (Chromium) and Firefox are the browsers covered by existing automated tests. Safari and iPad are not represented as supported platforms. If you test on another browser, record the browser name and exact version in every report — do not assume it is supported.

Supported beta inputs

The browser workbench currently presents these inputs. Test only the export type shown for your source.

ProfileInput
Local vault, Joplin, Google Keep, Bear, Craft, Anytype, DEVONthink, generic HTMLAn exported or unzipped folder
Evernote.enex or a ZIP of notebooks
NotionMarkdown page or Markdown/CSV ZIP export
OPML, Roam, generic CSV, Yummly, Tana.opml/.xml, .json, .csv, or .txt as labeled
Apple NotesFreENEXt Shortcut JSON export; generic HTML is a separate path

First conversion checklist

  1. Export from the source app and make a separate test copy. Do not point FreENxt at your only working vault.
  2. Open the browser workbench, select the matching source, and choose the small test copy.
  3. Keep the default safety setting that neutralizes unsafe attachment extensions unless your test specifically covers that option.
  4. Convert and download obsidian-vault.zip. Do not delete the source export.
  5. Extract the result into a new empty folder. Do not merge it into a production vault yet.
  6. Compare note counts, titles, folders, links, tags, dates, frontmatter, and representative attachments with the source copy.
  7. Open manifest.json and the on-screen conversion report. Review warnings, unsupported features, unresolved links, and attachment counts.
  8. Only after the sample is correct, repeat with a larger copy and verify again.

Privacy and trial expectations

  • For the browser conversion flow, selected file contents are processed in the browser tab and are not uploaded to FreENxt.
  • Optional analytics and diagnostics remain off unless you grant consent. Do not include note text, filenames containing personal data, email addresses, access tokens, or screenshots of private content in reports.
  • The local 7-day trial starts after the first successful conversion and is stored in that browser profile. Clearing browser storage, using private browsing, or changing profiles can affect local trial state.
  • Email submission after conversion is optional and is separate from file conversion.

Known beta limitations

  • Commerce is not part of the beta acceptance path. Do not test with a real purchase unless the beta coordinator explicitly confirms a live checkout.
  • Bitcoin/Lightning and fiat support controls may be unavailable while provider configuration is staged. Implemented payment code does not prove a live payment rail.
  • A successful conversion does not guarantee perfect fidelity. Encrypted, proprietary, or source-omitted content may be reported as unsupported.
  • The downloadable browser result targets an Obsidian-style Markdown vault; test other destinations only through their documented export paths.

Report a useful result without exposing data

Use the structured beta feedback form. Repository access may be required. Include:

  • FreENxt release SHA or release identifier, operating system, browser and version, and source type.
  • The numbered checklist step, expected behavior, actual behavior, and the exact error message after removing private content.
  • Only aggregate counts from the conversion report, such as notes found/written or unresolved-link count.
  • A minimal synthetic sample when reproduction requires input. Never attach your real export, license file, note contents, credentials, or personal identifiers.

If conversion fails, keep the original export untouched, close the tab, start again with a fresh copy and smaller sample, and record whether the failure repeats. General project support links are listed in Support the Developer; use the issue form for beta defects.