How three design sizes and Sermon Kit exports work

The build reviewed for this guide has three static canvases. Feed portrait is 1080×1350 at a 4:5 ratio. Square is 1080×1080 at 1:1. Story graphic is 1080×1920 at 9:16.

The file you receive depends on what you download. A one-page document downloads as a JPEG. If a document has several pages, one selected page downloads as a PNG. Select two or more pages and you receive one ZIP with a PNG for each page.

Those rules explain the files, but they do not remove the need to check them. A canvas size does not promise that every design converts into every ratio or fits every destination. It also cannot guarantee that the post stays readable after a platform adds its own crop and interface. Review each page before publishing it.

The three reviewed design canvases

These are design-document sizes. They describe the space used to compose a page.

They do not prove that every Sermon Kit page comes in all three versions. They also do not prove that a downloaded file will report the same pixel dimensions as the design canvas. Inspect the actual download before uploading it.

Feed portrait at 1080×1350

The 4:5 canvas gives a static design more vertical room than a square. That extra room can help a sermon quote, a short teaching point, or an announcement breathe without forcing every element into a compact block.

It also creates more room for a bad crop. A wide source photo may lose the subject at one side when it is placed in a portrait frame. A long quotation may fit inside the editor but become tiring on a phone. A heading that looks balanced at desktop scale may wrap into an awkward stack when viewed small.

Review the crop and the words together. If the image has a face, gesture, pulpit, scripture reference, or another meaningful detail, make sure the portrait composition keeps it.

Then reduce the page to about the size it will occupy on a phone. If a volunteer has to zoom in to check the sentence, the design is not ready.

Square at 1080×1080

The 1:1 canvas is useful when a balanced, compact composition fits the message. It can work for a brief quotation, a simple invitation, or a single teaching idea. It is also a useful fallback when a destination or downstream workflow expects a square asset.

Square is not a universal safe format. A destination may show a different profile-grid crop, add interface controls, or give portrait content more room in the feed. The same photograph may need a new focal point when moving from 4:5 to 1:1. The same copy may need fewer words or a different line break.

Do not treat the square page as a centre crop of the portrait page unless someone has inspected the result. The meaningful part of a photograph can sit near an edge. A scripture reference can disappear below a crop. A carousel marker can land where a platform places its own icon.

Story graphic at 1080×1920

The 9:16 canvas is a tall static graphic. It is not a Reel, video, animation, or proof of direct Story publishing.

Meta's current Reels guidance tells advertisers to keep key messages inside the safe zone for that full-screen placement. This supports a general caution about full-screen compositions, but it does not document the interface for a static Story.

Keeping essential words away from the outer edges is a sensible starting point. Before posting, open the current preview for the actual destination on a phone. Check whether its interface covers any text, logo, face, or call to action, then adjust the design to match what the preview shows.

Does one design automatically become all three sizes?

Do not assume that it does.

The reviewed build contains designs in the three canvas sizes. That is different from automatic conversion. A layout that works at 1080×1350 does not become a good 1080×1080 or 1080×1920 layout just because the software changes the boundary.

Real conversion needs decisions. The image may need a new crop. The heading may need a new position. A long quotation may need a shorter excerpt. Decorative elements that frame a square can leave a story graphic feeling empty. Elements near the bottom of a story can collide with destination controls.

Before buying on the strength of a size list, ask to see one ordinary sermon design in every format your team expects to use. Compare the wording, crop, hierarchy, and spacing. If the demonstration shows separate reviewed pages, that is useful. If it shows only a size selector, ask what happens to the layout after the selection.

The export rule depends on the document and selection

Church Media Kit does not present these three reviewed branches as a general format picker. The document structure and page selection determine what downloads.

A one-page document downloads as JPEG

When the document contains one page, the toolbar Export action acts on that page and downloads one .jpg file.

This is the direct single-page path. It does not mean every page in a larger Sermon Kit exports as JPEG. Once the document has several pages, the export selector changes the branch.

One selected page from a multi-page document downloads as PNG

When a document contains several pages, Export opens a page selector. If you choose one page and confirm, the reviewed path downloads one .png file for that selected page.

This distinction matters during a handoff. A teammate who expects a JPEG because they exported a one-page document last week may receive a PNG when they choose one page from this week's multi-page kit. The file is not wrong. It came through a different branch.

Two or more selected pages download as a ZIP of PNGs

If you select at least two pages in a multi-page document, the reviewed path downloads one .zip archive. Inside it is one PNG for each selected page.

The selector can start with all pages, narrow to the current page, use individual choices, or accept a page range. Selection is still a publishing decision. If a seven-page kit contains five approved pages, export those five. Do not include a page merely because it was selected by default.

The reviewed ZIP does not include a posting plan, captions, hashtags, alternative-text files, folders grouped by post, a PDF, an SVG, a PSD, video, or an editable source document. It is a package of selected PNG pages.

Review sequence before download

A clean export can preserve a bad decision perfectly. Review the content and order before pressing Export.

Start with the source. Compare direct quotations with the authorized sermon source. Check enough surrounding context to know whether the excerpt keeps the speaker's point. Remove quotation marks from a paraphrase. Verify scripture references, names, dates, service times, event details, and calls to action against a current source.

Then read multi-page content in order. A teaching carousel may fail if page three assumes that page two was included. A final invitation may make no sense without the preceding explanation. Check the selected set, not merely the full document.

Next, inspect each canvas as a design in its own right. Check the image crop, text fit, contrast, spacing, and reading order. WCAG 2.2 sets minimum contrast criteria for text, but passing a ratio does not make a dense graphic readable. Use the expected phone size and ask a second person to read it without coaching.

Finally, decide where the file is going. Feed, profile grid, Story, scheduled composer, and direct upload can show different previews. Platform behavior also changes. The destination preview is the last useful place to catch a crop or interface collision before a post goes live.

Check the downloaded files before handoff

Treat export as the start of a file check, not the end of approval.

For a JPEG or PNG, open the downloaded image outside the editor. Confirm that the expected page appears, the whole design is present, the correct font rendered, remote or uploaded images loaded, and no selection handles appear. Zoom out to phone size and zoom in enough to spot a missing glyph or broken image.

For a ZIP, extract it and count the PNG files. Compare that count with the pages you selected. Open the first, last, and any page with a complex image or unusual font. Then check the order in which the receiving teammate or destination will use them.

Keep the final caption, hashtags, and alternative text with the handoff in your church's approved system. They are not packaged by the reviewed export. Facebook, for example, lets a publisher add alternative text while editing a photo. W3C's image guidance explains how the image's purpose should shape that description.

Do not assume that text entered elsewhere in a design workflow becomes social-platform metadata. The person posting the file needs to add and verify the final destination fields.

A five-minute live-demo test for buyers

Use an ordinary authorized sermon graphic, not a polished sample chosen by the vendor.

1. Ask for one 4:5 feed-portrait page, one 1:1 square page, and one 9:16 story page.
2. Replace the headline with a realistic phrase from your church. Watch the line breaks in all three designs.
3. Replace the image with one your team is allowed to use. Inspect the focal point in each ratio.
4. Export a one-page document and confirm that the download is JPEG.
5. Open a multi-page document, select one page, and confirm that the download is PNG.
6. Select two or more pages, open the ZIP, and confirm that it contains one PNG per selected page.
7. Preview the files in the real destinations and devices your church uses.

This test will not prove reliability across every design, browser, or platform. It will answer the practical buying question: can your team understand the branches, review the pages, and hand off the files without guessing?

Where the reviewed workflow fits

The reviewed workflow may fit a church that wants static sermon designs in a small set of known canvases, is comfortable reviewing each ratio, and can add captions and accessibility details in its publishing process. The export branches are narrow enough to explain to a volunteer once the team understands the document rule.

It is a poor fit if the church requires automatic conversion between every ratio, broad format choice, editable source files, video output, a metadata-rich delivery package, or direct publishing from the same export action. It is also a poor fit if the team expects the software to approve crop, theology, source fidelity, readability, or pastoral judgment.

The best buying question is not "Does it have three sizes?" Ask whether the exact pages your church needs survive review, export, handoff, and destination preview. That is the work the size list cannot do for you.

Quick answers

What are the three reviewed design sizes?

Feed portrait is 1080×1350 at 4:5. Square is 1080×1080 at 1:1. Story graphic is 1080×1920 at 9:16.

What does a one-page document download?

The reviewed toolbar path downloads one JPEG.

What does one selected page from a multi-page document download?

It downloads one PNG.

What happens when I select several pages?

Two or more selected pages download as one ZIP containing one PNG per selected page.

Does the ZIP include captions, hashtags, alt text, or a posting plan?

No. The reviewed ZIP contains the selected PNG pages. Add and verify the other publishing material through your church's approved handoff and destination workflow.

Does Church Media Kit automatically convert every design into all three ratios?

This guide does not make that claim. Treat the ratios as distinct design canvases and review each page separately.