Fixing n8n File Previews: Why the 'View' Button Disappears and How to Resolve It

This n8n Community report describes a common integration friction: uploaded files surface in execution output but lack a 'View' preview button. n8n's UI renders a 'View' option only when a node returns binary data in the expected structure (binary field present with filename and mimeType). If the upload node stores content in JSON/text rather than the binary property, or if the filename/mimeType fields are missing or misnamed, the UI falls back to Download-only.

Troubleshooting steps: first, inspect the raw output of the last node (Execution -> Node -> Last Execution -> Data). Confirm the item includes a binary property (e.g., item.binary.myFile) with fields filename and mimeType. If mimeType is absent, set it explicitly using a Function/Set node or configure the incoming webhook/file node to include content-type. If your form stores Base64 in JSON, move that data into a binary property with the Move Binary Data node or via a Function node that creates the binary buffer and sets mimeType and filename.

Other considerations: trial account restrictions are unlikely to remove the View button-this is an application-level behavior. Also verify that the client-side form sends proper multipart/form-data rather than JSON-embedded Base64 unless you handle conversion. For previews, prefer web-viewable mime types (image/webp, image/png, application/pdf). If files are large, consider offloading to S3 and returning a signed preview URL to avoid memory pressure.

For business leaders, the operational lesson is to codify file handling standards and add automated validation to user submissions. Implement lightweight preprocessing nodes to normalize mime types and filenames, add monitoring of workflow failures tied to malformed uploads, and document the expected binary schema so front-end and back-end teams align-reducing support tickets and improving user experience.