Identify the document root and decide whether the new item should be publicly reachable. Private exports, credentials and logs generally belong outside a website document root. Check the application requirements before creating a configuration file that may change runtime behaviour.

1. Open Files in Plesk and navigate to the intended parent directory. Confirm the subscription and domain before continuing.
2. Use the new-item or plus control and choose Create Directory or Create File.
3. Enter a simple name with the correct extension. On Linux, names are case-sensitive, so Images and images can be different directories. Avoid spaces when application tooling does not support them.
4. Create the item, then use the appropriate text or code editor if a file needs content. An empty file is not a working page or configuration by itself.
5. Review the inherited permissions and ownership. Follow the application requirements; do not grant broad write permission just because a file is new.

Confirm the item appears in the expected directory and contains the intended content. If it should be public, request its exact URL and verify the response. If it should remain private, verify that it is outside the public document root and not exposed through another site mapping.

If creation fails, check quota, permissions and whether an item already has the same name. A leading-dot file may be hidden by a display filter. Do not overwrite an existing application file simply to clear a duplicate-name error; preserve the original and review its purpose first.

• Uploading website files with Plesk File Manager
• Editing a website file safely in Plesk
• Checking disk space and traffic usage in Plesk
• Changing the language of your Plesk interface

• Plesk: Uploading Content With File Manager