Batch Text Processing on Mac

Start with the text operation you need: extract URLs, remove blank lines, trim spaces or change a repeated identifier. Choose a ready-made script, or write a JavaScript run(ctx) function for your own rule. One function can perform several text transformations before returning its result.

The real JS Script window below has Extract URLs selected. It collects matching HTTP and HTTPS links from the supplied text, one per line. The script preserves their order and keeps duplicate matches, so extracting links and removing duplicates are separate choices.

Built-in scripts are marked Built-in · Read Only. Choose Copy as My Script if you want to edit the rule and save a named version under My Scripts. You can run that saved script on one document or select it for a whole directory.

Use Demo to try the built-in sample without changing your open document. Once the result is right, use the workspace controls to choose the real folder targets.

Open the workspace folder, select Extract URLs and narrow the batch targets to TXT files. The script runs on each selected file; the App manages opening the files and writing approved results. The JavaScript itself does not need file-system access.

This sample contains release-links.txt and incident-links.txt in the root folder, plus team/reference-links.txt in a subfolder. README.md explains the example and is excluded by the TXT filter.

Read the names and relative paths in the confirmation window. Choose Preview mode (no disk writes) to calculate the proposed results first. This workflow changes the contents of the selected files, while their names remain the same.

The opening screenshot shows the Extract URLs result for release-links.txt. The source contains Docs, Preview and repeated-link labels. Result View contains the three matching URLs, one per line. The documentation link still occurs twice because the built-in rule preserves duplicate matches.

Review each target file, including files in subfolders. A result that is correct for one document does not prove every other input has the format you expected. The table below summarizes the outputs for this sample workspace.

Preview mode leaves the original files unchanged. Apply and Apply All are separate write actions; choose them after checking the proposed changes. This script extracts URL text locally and does not fetch the linked pages.

After applying the reviewed changes, open Operation History for the same workspace. The real operation details below identify Extract URLs and list the three modified TXT files.

Each file has a Diff control and an Available backup status in this capture. Use the per-file details to inspect what changed, and read the outcome for errors or skipped files.

The operation shown here has a backup for each modified file. With backup creation enabled, a failed backup stops the affected write and is reported as an error. Check that backups are available before relying on restoration.

Choose Restore this operation from the operation details to recover the backed-up contents. In this demonstration, the three TXT files are restored to their original labelled text; the excluded README.md remains unchanged.

Batch backups are retained for seven days. Files edited since the batch operation, or open with unsaved changes, are skipped during restoration so a newer edit is not overwritten. Missing or expired backups cannot be restored.

Read the restoration result for skipped files or errors, and keep your normal backups for important work.

For a different job, write or adapt your own script and save it under My Scripts. A single JavaScript function can trim spaces, filter lines, remove duplicates and sort the result, or perform a completely different text transformation.

The separate real preview below shows a custom rule named Demo - OLD to NEW. It replaces OLD- with NEW- only at the beginning of each line. Four ID lines change; duplicate IDs, their order and blank lines remain.

This capture illustrates the single-document Cancel and Apply to Document controls. Once the result matches your intent, select that custom script in the workspace batch controls, choose the folder targets and preview each file before applying it.

Save a rule you use repeatedly, pin it to the main toolbar and assign an available script shortcut. The script remains the same whether you run it on one document or reuse it across selected workspace files.

AI Guide provides instructions for the App’s script format. For editable scripts, the optional AI Script Assistant can help create or modify code after you configure your provider and API access. The assistant requires Pro access or an eligible trial, and the provider may charge for use. Review the generated code and test its output.

Ordinary text-processing scripts run locally. AI is optional, and scripts do not get direct access to arbitrary files, the network or system commands. The App manages access to the documents and workspace folder you authorize.