This conversation was generated with Duck.ai (https://duck.ai) using OpenAI's GPT-4o mini Model. AI chats may display inaccurate or offensive information (see https://duckduckgo.com/duckai/privacy-terms for more info).
====================
User prompt 1 of 11: how to import media to ghost
Assist: To import media to Ghost, you can use the built-in importer found in the Settings → Advanced → Import/Export area of Ghost Admin. You can upload images and content by adding them to a zip file, ensuring they follow the correct file path structure for successful import.
Relevant sources:
User prompt 2 of 11 - 25/01/2026, 13:45:36: What is the file structure required?
GPT-4o mini: To import media into Ghost effectively, you need to follow a specific file structure when creating your ZIP file. Here's a breakdown of the required structure:
-
Root Folder
- This should be the main folder that you zip.
-
Subfolders
- Create subfolders based on the content type. For example:
- /images: Store all your image files here.
- /videos: Store any video files here (if applicable).
- /audio: For audio files, if needed.
- Create subfolders based on the content type. For example:
-
File Naming
- Each media file should have a unique name to avoid conflicts. Use simple, descriptive names without special characters.
/MyMediaImport
/images
- image1.jpg
- image2.png
/videos
- video1.mp4
/audio
- audio1.mp3
- File Types: Ensure you are using supported file types (e.g., JPG, PNG for images; MP4 for videos).
- Compression: Once your folders and files are organized, compress the root folder into a ZIP file for upload.
- Paths: Maintain the file path structure to ensure Ghost can locate your files during the import process.
Following this structure will help ensure a smooth import process into Ghost.
User prompt 3 of 11 - 25/01/2026, 13:46:27: What about the post and page content? Where does that go?
GPT-4o mini: When preparing to import post and page content into Ghost along with your media, you'll need to include specific structures for your content as well. Here's how to organize that:
-
Root Folder
- This is the main folder containing everything you wish to import.
-
Subfolders
- Similar to media, create a subfolder for your content:
- /content: This will hold your Markdown or JSON files representing your posts and pages.
- Similar to media, create a subfolder for your content:
-
Content Files
- Each post or page should be saved as a separate Markdown (.md) or JSON (.json) file.
- Use descriptive filenames, possibly including the date for easier identification.
/MyMediaImport
/images
- image1.jpg
- image2.png
/videos
- video1.mp4
/audio
- audio1.mp3
/content
- post1.md
- post2.md
- page1.md
- Each Markdown file should start with a YAML front matter block that contains metadata for posts and pages, such as:
---
title: "Your Post Title"
date: "2026-01-25"
tags: ["tag1", "tag2"]
status: "published" # or "draft"
---
Your post content goes here.If using JSON, the general structure might resemble:
{
"posts": [
{
"title": "Your Post Title",
"slug": "your-post-title",
"date": "2026-01-25",
"tags": ["tag1", "tag2"],
"content": "Your post content goes here.",
"status": "published" // or "draft"
}
]
}Ensure your files are organized within these structured folders to facilitate a seamless import process for both media and content into Ghost. By adhering to this organization, Ghost can accurately process and recognize your posts, pages, and accompanying media.
User prompt 4 of 11 - 25/01/2026, 13:47:42: The documents for ghost refer to a specific JSON file schema for imports, and don't mention importing posts as markdown files. is this definitely possible?
GPT-4o mini: You are correct; Ghost primarily supports the import of content through a specific JSON schema, not Markdown files. The JSON format allows for a structured and organized approach to importing posts and pages, ensuring compatibility with Ghost's framework.
-
Root Folder
- Create a main folder to contain your import files.
-
Content Folder
- Inside this root folder, you should have a /content folder containing the JSON file.
The JSON file must adhere to Ghost's specific schema for posts and pages. Here’s a basic outline of the expected format:
{
"posts": [
{
"title": "Your Post Title",
"slug": "your-post-title",
"markdown": "Your post content goes here.",
"status": "published",
"published_at": "2026-01-25T00:00:00.000Z",
"tags": [{
"name": "tag1"
}]
}
],
"pages": [
{
"title": "Your Page Title",
"slug": "your-page-title",
"markdown": "Your page content goes here.",
"status": "published",
"published_at": "2026-01-25T00:00:00.000Z"
}
]
}- Markdown Field: The content of posts and pages should be included in the
markdownfield. - Content Types: Ensure you distinguish between
postsandpagesin your JSON file as shown above. - Media References: If images or media are included within your post content, ensure that those files are either uploaded separately or linked correctly in the content.
To import content into Ghost, use the JSON file following the specified schema. Markdown files are not supported for direct import. Structuring your content as per Ghost's guidelines will facilitate a successful import process.
User prompt 5 of 11 - 25/01/2026, 13:48:48: So can the JSON schema file and the media files be imported in a single step using this zip archive method?
GPT-4o mini: Yes, you can import both the JSON schema file for your posts and pages, along with your media files, in a single step using a ZIP archive. Here’s how to do it:
-
Create the Main Folder
- This will be the root folder for your import, which you will later compress into a ZIP file.
-
Organize Your Content
- Inside this main folder, you will have the following structure:
- /content: This should contain your
import.jsonfile, which follows the required JSON schema. - /images (or /media): Store any images or media files you want to include.
- /content: This should contain your
- Inside this main folder, you will have the following structure:
/MyMediaImport
/content
- import.json
/images
- image1.jpg
- image2.png
- Create your import.json file in the /content folder.
- Place all related media files in the designated /images (or /media) folder.
- Compress the main folder (MyMediaImport) into a ZIP file.
- Navigate to the Settings in Ghost Admin.
- Go to Advanced, and select Import/Export.
- Upload your ZIP file containing the content folder with the import.json and your media files.
This method allows you to import both your content structured in JSON and any associated media files in one step, streamlining the process and ensuring that everything is properly organized and accessible within Ghost.
User prompt 6 of 11 - 25/01/2026, 13:49:32: Where post content references an image, how should that be represented in the JSON?
GPT-4o mini: When including image references in your JSON for Ghost, you need to ensure that the images are correctly linked in the post content. Here’s how to represent images in the JSON file:
-
Upload Media: Ensure that the images are uploaded and available in the Ghost Admin or included in your ZIP under the
/imagesfolder. -
Markdown Syntax: Use Markdown syntax to reference the images directly in the
markdownfield of your post or page. The link should point to the correct URL where the image is stored.
Here’s how you can structure a post with an image reference:
{
"posts": [
{
"title": "Your Post Title",
"slug": "your-post-title",
"markdown": "Here is an image of a beautiful landscape:\n",
"status": "published",
"published_at": "2026-01-25T00:00:00.000Z",
"tags": [{
"name": "Nature"
}]
}
]
}- Markdown Syntax: Use the
format to include images in the content. - Relative Path: If you are importing the images as part of the ZIP file, the path (e.g.,
/images/landscape.jpg) should correctly point to the location within the Ghost installation where images can be accessed. - Alt Text: Always include descriptive alt text for better accessibility and SEO.
By using the Markdown syntax, you can seamlessly include image references in your JSON content for Ghost, ensuring they are displayed correctly in your posts. Make sure the paths are correct to enable the images to render properly on the front end.
User prompt 7 of 11 - 25/01/2026, 13:51:55:
So just to confirm, the URLs used in ghost content export JSON files should not be used here? Specifically, they look like this: __GHOST_URL__/content/images/2026/01/a-picture.png
GPT-4o mini:
Yes, you are correct. When creating the import JSON file for Ghost, you should NOT use the URLs formatted as __GHOST_URL__/content/images/2026/01/a-picture.png.
-
Local Reference vs. Absolute URLs:
- In your import JSON, it is more appropriate to use relative paths instead of the absolute URL format that might appear in exported content or public-facing URLs.
-
Relative Path Workaround:
- Reference the images as relative paths in the Markdown content:
- For example:
- For example:
- This assumes that, after the import, the images would be accessible under the Ghost installation's structure.
- Reference the images as relative paths in the Markdown content:
If your image is included in the ZIP under the /content/images folder, use:
{
"posts": [
{
"title": "Sample Post",
"slug": "sample-post",
"markdown": "Check out this image:\n",
"status": "published",
"published_at": "2026-01-25T00:00:00.000Z"
}
]
}In summary, use relative paths for your image references in the import JSON. This approach ensures that Ghost can correctly interpret and render the images after the import process. Avoid using the __GHOST_URL__ placeholder or absolute URLs.
User prompt 8 of 11 - 25/01/2026, 13:53:04: The path you gave as an example in point two is not a relative path?
GPT-4o mini: You're right, and I appreciate your attention to detail. The example path I provided is indeed not a true relative path as it assumes a specific directory for the Ghost installation.
- A relative path should refer to the location of files in relation to the current directory without including the base URL or domain.
- For example:
- If the images are in a folder within the
contentdirectory of your Ghost setup after import, that folder structure might allow you to reference files simply by their name or using paths that don't specify the entire URL structure.
- If the images are in a folder within the
If your images are intended to be uploaded to /content/images/, you would typically reference them just by:
Here’s how you should represent it in your JSON:
{
"posts": [
{
"title": "Sample Post",
"slug": "sample-post",
"markdown": "Check out this image:\n",
"status": "published",
"published_at": "2026-01-25T00:00:00.000Z"
}
]
}Using a path like images/sample-image.jpg assumes that the images directory is accessible relative to the installation's document root or the current working directory of the import. I appreciate your patience and clarification on this topic!
User prompt 9 of 11 - 25/01/2026, 13:53:55: Also, is it possible to import markdown via a "markdown" field as in this example? I've not seen this in the documentation
GPT-4o mini: You’re correct; the Ghost import functionality primarily utilizes JSON for content and does not support importing posts via a "markdown" field in the JSON schema.
-
JSON Schema: Ghost requires all post and page content to be formatted according to a specific JSON schema. Each post’s content must be included in the
htmlormobiledocfield. -
Markdown vs. HTML: While you can write your content in Markdown, when importing, it should ideally be converted to HTML format for compatibility. Ghost does not have a designated
markdownfield for imports in the JSON schema.
Here’s how to structure a post with content in HTML format in your JSON:
{
"posts": [
{
"title": "Sample Post",
"slug": "sample-post",
"html": "<p>Check out this image:</p><img src=\"/content/images/sample-image.jpg\" alt=\"Sample Image\" />",
"status": "published",
"published_at": "2026-01-25T00:00:00.000Z"
}
]
}In summary, for importing posts into Ghost, use the html or mobiledoc field in the JSON schema to include your content. The use of a markdown field is not supported in the import process, ensuring that all content is properly formatted and rendered. Thank you for checking, and I hope this clears up any confusion!
User prompt 10 of 11 - 25/01/2026, 13:54:26: Is it possible to use the "lexical" field to import content instead of "html"?
GPT-4o mini: Yes, you can use the "lexical" field in the JSON schema to import content into Ghost, which allows for a more advanced content structure. The lexical format is a part of Ghost's efforts to modernize content handling and supports richer text editing.
-
Field Availability: The
lexicalfield is designed to accommodate structured content created with Ghost's new rich text editor. This format captures more than just plain text, allowing for inline elements, formatting, and media. -
Content Format: When using the
lexicalfield, content is represented in a manner tailored for Ghost's rich text capabilities, making it easier to manipulate and render complex content.
Here’s how you can structure a post using the lexical field in your JSON:
{
"posts": [
{
"title": "Sample Post",
"slug": "sample-post",
"lexical": {
"root": {
"children": [
{
"type": "paragraph",
"children": [
{
"text": "Check out this image:"
}
]
},
{
"type": "image",
"src": "/content/images/sample-image.jpg",
"alt": "Sample Image"
}
]
}
},
"status": "published",
"published_at": "2026-01-25T00:00:00.000Z"
}
]
}Using the lexical field is a valid approach for importing content into Ghost, especially if you want to take advantage of richer text formatting and structure. It allows for more flexibility compared to the html field, making it suitable for modern content requirements.
User prompt 11 of 11 - 25/01/2026, 13:55:14: Have you got a reference for this?
GPT-4o mini: You can reference the following sources for detailed information regarding the use of the lexical field in Ghost's JSON imports:
-
Importing Content Documentation:
- Ghost provides documentation on how to import content, including the structure of the JSON file. You can access the official guide here.
-
Developer Migration Docs:
- This section outlines the JSON structure you should use, including various fields such as
htmlandlexical. The information is available in the Ghost Developer Documentation.
- This section outlines the JSON structure you should use, including various fields such as
-
Walking through Example Imports:
- A user blog post that details various import scenarios, including working with the HTML or lexical formats, can be seen in this article: Importing posts into Ghost.
These resources should help clarify how to properly use the lexical field for content imports into Ghost. If you need more specifics, feel free to ask!
